Horton

Re: Shaky coding for vacuuming partitioned relations

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-09-25T11:22:44Z
Lists: pgsql-hackers 
On Mon, Sep 25, 2017 at 7:57 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> FWIW, the same thing can happen when specifying an invalid replication
> origin name to pg_replication_origin_advance() and
> pg_replication_origin_progress(). These probably should fixed as well.

I have spawned a thread about that stuff three weeks ago:
https://www.postgresql.org/message-id/CAB7nPqQtPg%2BLKKtzdKN26judHcvPZ0s1gNigzOT4j8CYuuuBYg%40mail.gmail.com
With a patch registered where it should be:
https://commitfest.postgresql.org/15/1290/
So I would suggest to keep the discussions about this problem in its own thread.

(Bonus: ALTER TABLE queries in parallel with multiple sessions and
enjoy the result)
-- 
Michael

Commits

  1. Fix inadequate locking during get_rel_oids().