Re: Documentation update (pg_get_fkeydef, current_database) - Mailing list pgsql-patches

From Tom Lane
Subject Re: Documentation update (pg_get_fkeydef, current_database)
Date
Msg-id 10110.1029348946@sss.pgh.pa.us
Whole thread Raw
In response to Re: Documentation update (pg_get_fkeydef, current_database)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Uh, I was going to add current_database() patch in the patch queue.  Is
> that OK?  I can apply only that part of the doc patch.

current_database looks pretty harmless.  I want to look at get_fkeydef
or whatever it was called, though.

>> I still have to finish up the tail-end work of reviewing Rod'
>> constraints patch, and this stuff is part of that ... it's back to
>> pg_dump for the next couple days for me ...

> Which one was that?

The stuff involving changing the way that pg_dump deals with constraints
and foreign keys and serials (at least two different patches I think).
get_fkeydef is backend support for that.

> Where are we on the prepare statement patch?  I saw
> another version appear yesterday or the day before.

I haven't looked at the latest version yet.

            regards, tom lane

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: [HACKERS] [GENERAL] workaround for lack of REPLACE() function
Next
From: Jan Wieck
Date:
Subject: Re: [SQL] 16 parameter limit