From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump future problem. |
Date: | 2003-05-04 14:01:45 |
Message-ID: | 27556.1052056905@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> I see an obvious problem in the way pg_dump dumps serials. At the moment,
> we have length 64 identifiers. If someone has a 64 character table name
> and adds a serial to it, it will get a truncated sequence name, with _seq
> o the end.
> However, if we up 7.4, say, to use 128 character identifiers, then this
> restore will fail, as the sequence name will NOT be truncated and the
> setval() call will fail.
<yawn> ... AFAIR, we have heard no reports of such problems with the
32-to-64 name conversion. The odds of problems with a (hypothetical)
future increase to 128 would be far less.
I think we have more immediate problems to worry about.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-04 14:10:22 | Re: pg_dump future problem. |
Previous Message | brian janaszek | 2003-05-04 13:57:09 | Slackware 9 Build Problems |