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 3887.1497986333@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Something is rotten in publication drop  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Something is rotten in publication drop
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jun 19, 2017 at 9:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> Should we add that to the opr_sanity tests?

Yeah, I was wondering about that too.  I can imagine that someday
there will be prosecdef built-in functions ... but probably, there
would never be so many that maintaining the expected-results list
would be hard.
        regards, tom lane



pgsql-hackers by date:

Previous
From: J Chapman Flack
Date:
Subject: Re: [HACKERS] postgresql transactons not fully isolated
Next
From: Chapman Flack
Date:
Subject: Re: [HACKERS] postgresql transactons not fully isolated