> -Original Message-
> From: Merlin Moncure [mailto:mmonc...@gmail.com]
> Sent: Friday, October 28, 2011 8:29 PM
> To: Dmitry Epstein
> Cc: t...@sss.pgh.pa.us; pgsql-general@postgresql.org; Peter Gagarinov
> Subject: Re: [GENERAL] nextval skips values between consecutive calls
>
> On Fri,
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Friday, October 28, 2011 7:22 PM
> To: Dmitry Epstein
> Cc: pgsql-general@postgresql.org; Peter Gagarinov
> Subject: Re: [GENERAL] nextval skips values between consecutive calls
>
> writes:
> > -- This is rather sur
I just found an odd thing about nextval (PostgreSQL 9.0): When nextval is
called together with a function returning a sequence, such as generate_series
or unnest, it skips one value between consecutive calls:
create sequence test_sequence;
-- This works as expected
select nextval(' test_sequenc
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of J.V.
> Sent: Friday, October 21, 2011 1:11 AM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] how to disable all pkey/fkey constraints globally
>
> Is the
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of thomas veymont
> Sent: Wednesday, October 05, 2011 5:35 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] gaps/overlaps in a time table : current and previous
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of J.V.
> Sent: Tuesday, October 04, 2011 10:00 PM
> To: pgsql-general
> Subject: [GENERAL] how to disable all pkey/fkey constraints globally
>
> Is there a generic way
Until v. 9.1 enum modification was not officially supported, although hacking
pg_enum made it somewhat workable. Since v. 9.1 there is a way to add values to
enum types. However,
- alter type ... add value doesn't work in transaction blocks, which severely
limits its usefulness
- there is still
