Re: [HACKERS] Something is rotten in publication drop - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Something is rotten in publication drop
Date
Msg-id 25259.1497923852@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Something is rotten in publication drop  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Something is rotten in publication drop  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: [HACKERS] Something is rotten in publication drop  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: [HACKERS] Something is rotten in publication drop  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> If there are no new insights, I plan to proceed with the attached patch
> tomorrow.  This leaves the existing view and function alone, adds
> pg_relation_is_publishable() and uses that in psql.

Hm, patch looks okay, but while eyeballing it I started to wonder
why in the world is pg_get_publication_tables marked prosecdef?
If that has any consequences at all, they're probably bad.
There are exactly no other built-in functions that have that set.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Get stuck when dropping a subscription duringsynchronizing table
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] Rules on table partitions