From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kris Kiger <kris@musicrebellion.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Pgsql-Admin (E-mail) <pgsql-admin@postgresql.org>
Subject: Re: Very worried about this
Date: Thu, 24 Mar 2005 16:57:41 -0500
Message-ID: <8650.1111701461@sss.pgh.pa.us> (raw)
In-Reply-To: <424334DE.4020908@musicrebellion.com>
References: <42432F48.8060103@musicrebellion.com>
<1111700264.12450.10.camel@state.g2switchworks.com>
<424334DE.4020908@musicrebellion.com>
Kris Kiger <kris@musicrebellion.com> writes:
> I'm positive no one else has been in the database. There are two of us
> who work on it and we have been side by side all afternoon. The problem
> appears to be purely internal to the database. I'm running more tests
> as we speak and we are still recieving the same sporadic errors.
Well, it would be good to positively refute Scott's theory. Let's see
select max(d_id) from hd;
and
select * from hd_d_id_seq;
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, kris@musicrebellion.com, smarlowe@g2switchworks.com
Subject: Re: Very worried about this
In-Reply-To: <8650.1111701461@sss.pgh.pa.us>
References: <42432F48.8060103@musicrebellion.com> <1111700264.12450.10.camel@state.g2switchworks.com> <424334DE.4020908@musicrebellion.com> <8650.1111701461@sss.pgh.pa.us>
* 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