Re: pg_dump future problem.
| От | Tom Lane |
|---|---|
| Тема | Re: pg_dump future problem. |
| Дата | |
| Msg-id | 27556.1052056905@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | pg_dump future problem. (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
| Список | pgsql-hackers |
Christopher Kings-Lynne <chriskl@familyhealth.com.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
В списке pgsql-hackers по дате отправления: