From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Proposed patch for sequence-renaming problems |
Date: | 2005-10-01 19:09:19 |
Message-ID: | 200510011909.j91J9Jr13956@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> Does that sound like a workable compromise?
>
> > Personally, I _love_ it. I hope others do as well. :-)
>
> OK, I'll work up a patch.
Here is a query that shows nextval(::text) usage as defaults:
SELECT n.nspname, c.relname, a.attname, d.adsrc
FROM pg_namespace n, pg_class c, pg_attribute a, pg_attrdef d
WHERE n.oid = c.relnamespace AND
c.oid = a.attrelid AND
a.attrelid = d.adrelid AND
a.attnum = d.adnum AND
d.adsrc ~ '.*nextval\\(''[^'']*''::TEXT\\)';
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-10-01 19:28:58 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
Previous Message | Simon Riggs | 2005-10-01 18:59:11 | Re: effective SELECT from child tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-10-01 19:28:58 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
Previous Message | Tom Lane | 2005-10-01 18:47:51 | Re: [PATCHES] Proposed patch for sequence-renaming problems |