From: Neil Conway <neilc@samurai.com>
To: Justin Clift <justin@postgresql.org>
Cc: Oliver Elphick <olly@lfix.co.uk>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [GENERAL] Bug with sequence
Date: 20 Nov 2002 22:44:06 -0500
Message-ID: <877kf74mex.fsf@mailbox.samurai.com> (raw)
In-Reply-To: <3DDC47A9.4C0BC2DE@postgresql.org>
References: <92c0776e.0211180745.49911131@posting.google.com>
<1037782392.29678.88.camel@linda>
<1037828113.23925.101.camel@camel>
<1037830378.24840.40.camel@linda>
<3DDC47A9.4C0BC2DE@postgresql.org>
Justin Clift <justin@postgresql.org> writes:
> This sounds like a serious bug in our behaviour, and not something
> we'd like to release.
It's not ideal, I agree, but I *definately* don't think this is
grounds for changing the release schedule.
> No real issue with the nicety for newbies, but am very concerned
> about the lack of a dependancy check here.
Well, how would you suggest we fix this? ISTM this is partially a
result of the fact that we don't produce dependancy information for
function bodies. While it might be possible to do so (in 7.4) for
certain types of functions (e.g. for functions defined in SQL,
PL/PgSQL, etc.), I can't see a general solution (e.g. for functions
defined in C).
And adding random hacks to get specific functions (e.g. nextval()) to
work does not strike me as a very good idea.
Cheers,
Neil
--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: neilc@samurai.com, justin@postgresql.org, olly@lfix.co.uk, xzilla@users.sourceforge.net, pgsql-hackers@postgresql.org
Subject: Re: [GENERAL] Bug with sequence
In-Reply-To: <877kf74mex.fsf@mailbox.samurai.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox