Re: [HACKERS] Logging for sequences

2000-12-06 Thread Tom Lane
Philip Warner <[EMAIL PROTECTED]> writes: > At 17:39 29/11/00 -0800, Mikheev, Vadim wrote: >> BTW, why SETVAL is called in pg_dump output instead of >> if (called) NEXTVAL? SETVAL is disallowed for sequences >> with cache_value > 1 - ie we can't dump such sequences now. > Can someone explain this

RE: [HACKERS] Logging for sequences

2000-12-06 Thread Mikheev, Vadim
> Vadim, Philip changed that part of pg_dump on my advice. The idea was > to try to do the right thing for sequences when loading schema only or > data only. Analogously to loading data into a pre-existing table, we > felt that a data dump ought to be able to restore the current state of > an al

Re: [HACKERS] Logging for sequences

2000-11-29 Thread Philip Warner
At 17:39 29/11/00 -0800, Mikheev, Vadim wrote: >is done. Initdb is required, sorry. > >BTW, why SETVAL is called in pg_dump output instead of >if (called) NEXTVAL? SETVAL is disallowed for sequences >with cache_value > 1 - ie we can't dump such sequences now. Can someone explain this to me? It's