Re: [PATCHES] Proposed patch for sequence-renaming problems

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PATCHES] Proposed patch for sequence-renaming problems
Дата
Msg-id 8762.1128182268@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: [PATCHES] Proposed patch for sequence-renaming problems  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Hold, I think I see an idea here.  We have two cases, those for SERIAL
> and those for manual nextval() in DEFAULT.  For SERIAL, we can easily
> map to a nextval(::regclass) call on pg_dump reload.  For manual
> nextval, it will appear in the dump as nextval('myseq'::text), and Tom
> is saying that will be late binding.

> I think we can live with SERIAL working fine on reload, and requiring
> users who created a manual default using nextval() to ALTER TABLE
> DROP/SET DEFAULT to remove the ::text marker if they want early binding.

"Removing the ::text marker" isn't going to work, because if we have
both nextval(regclass) and nextval(text) then the latter is going to
capture any cases with an unknown literal.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Jim C. Nasby"
Дата:
Сообщение: Re: effective SELECT from child tables
Следующее
От: "Jim C. Nasby"
Дата:
Сообщение: Re: effective SELECT from child tables