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: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Generate user/group sysids from a sequence? |
Date: | 2003-01-17 17:01:01 |
Message-ID: | 12804.1042822861@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK. Do we have many people left upgrading from pg_dump's that COPY into
> pg_shadow?
Hm, good point. I had forgotten we ever did that ;-)
It looks like 7.0.* was the last release where pg_dumpall did that.
Is that far enough back?
[ looks further... ] Actually, such a dump is broken now anyway,
because the column layout of pg_shadow has changed since 7.0.
So I think it's a moot point.
We could perhaps arrange the code so that if nextval'ing the sequence
produces a duplicate sysid, we just loop back and nextval again until
we get a nonconflicting id. I had hoped to remove the seqscan of
pg_shadow from CREATE USER; but we could replace it with syscache probes
for duplicate usename and id, and just repeat the syscache probe if
we have to do another nextval. This way, we don't need to bother with
touching the sequence at all during a CREATE USER with explicit sysid.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 2003-01-17 17:20:12 | Re: Generate user/group sysids from a sequence? |
Previous Message | Bruce Momjian | 2003-01-17 16:50:39 | Re: Win32 port |