ARTEAGA Jose wrote:
I have spent the last month battling and looking deeper into the issue,
here's a summary of were I'm at:
- Increasing shared buffers improved performance but did not resolve the
backend FATAL disconnect error.
- Dumping and recreating entire database also did not resolve the
, 456c48, 455bd0) + db0
Rgds/
Jose Arteaga
-Original Message-
From: ARTEAGA Jose
Sent: Thursday, June 07, 2007 12:32 PM
To: Alvaro Herrera; Richard Huxton
Cc: pgsql-general@postgresql.org
Subject: RE: [GENERAL] Limitations on 7.0.3?
I've looked at the pg_index table and we are currently
Richard Huxton [EMAIL PROTECTED] writes:
I think tag_hash (in /backend/utils/hash/hashfn.c) is responsible for
internal hash-tables (rather than hash indexes). It takes a pointer to a
key to hash and a keysize (in bytes), so either the pointer is bad or
the size is too long and it's reading
gold. But cannot claim victory yet it's only
been up for 2 days.
-Jose
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 07, 2007 7:02 AM
To: Richard Huxton
Cc: ARTEAGA Jose; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Limitations on 7.0.3
On Thu, Jun 07, 2007 at 02:32:09PM -0500, ARTEAGA Jose wrote:
I've looked at the pg_index table and we are currently at 15Mill
entries, which should be OK. After 2-3 days runtime I just get a
disconnect error from backend while doing an insert. After I restore the
DB and insert the same
Martijn van Oosterhout wrote:
On Thu, Jun 07, 2007 at 02:32:09PM -0500, ARTEAGA Jose wrote:
I've looked at the pg_index table and we are currently at 15Mill
entries, which should be OK. After 2-3 days runtime I just get a
disconnect error from backend while doing an insert. After I restore the
ARTEAGA Jose wrote:
Also worth mentioning is that I just this week found out about a very,
very important parameter shared buffers. Ever since the original
person setup our PG (individual no longer with us) this DB had been
running without any major glitches, albeit slow. All this time the
I have been using postgres 7.0.3 (Solaris 2.9) for the past 4 years
without any major problems, until about a month ago. We are now
experiencing crashes on the backend (connection lost to backend) while
running queries (inserts, etc). Anyway I don't want to make this too
technical but I'd just
ARTEAGA Jose wrote:
I have been using postgres 7.0.3 (Solaris 2.9) for the past 4 years
without any major problems, until about a month ago. We are now
experiencing crashes on the backend (connection lost to backend) while
running queries (inserts, etc). Anyway I don't want to make this too
Richard Huxton wrote:
ARTEAGA Jose wrote:
I have been using postgres 7.0.3 (Solaris 2.9) for the past 4 years
without any major problems, until about a month ago. We are now
experiencing crashes on the backend (connection lost to backend) while
running queries (inserts, etc). Anyway I don't
On Wed, Jun 06, 2007 at 02:40:08PM -0500, ARTEAGA Jose wrote:
I have been using postgres 7.0.3 (Solaris 2.9) for the past 4 years
without any major problems, until about a month ago. We are now
experiencing crashes on the backend (connection lost to backend) while
running queries (inserts,
11 matches
Mail list logo