Travis,
We have used postgresql 7.4, 8.0, and 8.1 with DSPAM and have
never had a single problem like you are describing. In the past
on this mailing list, these sorts of issues have been caused by
hardware problems on the DB server in some cases. Good luck with
tracking it down.
Ken
On Tue, Jun
On Tue, Jun 06, 2006 at 12:58:10PM -0400, Travis Cross wrote:
> >Do you *know* that the disk drive will not lie about write
> >complete?
>
> "Know" is such a strong word ;) Honestly, I have very little idea.
> I understand the nature of the problem this presents, as I've read
> the very fine P
Ian Barwick wrote:
On 6/6/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Travis Cross <[EMAIL PROTECTED]> writes:
> I'm noticing that a handful (4-16) of rows with duplicate columns
> (uid,token) are sneaking into the table every day despite the
> primary key constraint.
Corrupt index, looks like ...
Tom Lane wrote:
Travis Cross <[EMAIL PROTECTED]> writes:
I'm noticing that a handful (4-16) of rows with duplicate columns
(uid,token) are sneaking into the table every day despite the
primary key constraint.
Corrupt index, looks like ... you might try reindexing the index.
I probably should
Kenneth Marshall wrote:
We have used postgresql 7.4, 8.0, and 8.1 with DSPAM and have
never had a single problem like you are describing. In the past
on this mailing list, these sorts of issues have been caused by
hardware problems on the DB server in some cases. Good luck with
tracking it down.
On 6/6/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Travis Cross <[EMAIL PROTECTED]> writes:
> I'm noticing that a handful (4-16) of rows with duplicate columns
> (uid,token) are sneaking into the table every day despite the
> primary key constraint.
Corrupt index, looks like ... you might try reinde
Travis Cross <[EMAIL PROTECTED]> writes:
> I'm noticing that a handful (4-16) of rows with duplicate columns
> (uid,token) are sneaking into the table every day despite the
> primary key constraint.
Corrupt index, looks like ... you might try reindexing the index.
I don't believe that the PANIC y
I have a table that I am using to store email token data for DSPAM.
I'm noticing that a handful (4-16) of rows with duplicate columns
(uid,token) are sneaking into the table every day despite the
primary key constraint.
The server currently processes a few thousand emails per day, and
this parti
