From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Rod Taylor <rbt(at)zort(dot)ca>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Documentation update (pg_get_fkeydef, current_database) |
Date: | 2002-08-14 18:15:46 |
Message-ID: | 10110.1029348946@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2002-08-14 18:30:53 | Re: [SQL] 16 parameter limit |
Previous Message | Joe Conway | 2002-08-14 18:09:41 | Re: [HACKERS] [GENERAL] workaround for lack of REPLACE() function |