Tom Lane wrote:
Alex Adriaanse [EMAIL PROTECTED] writes:
Unfortunately, we do not have any core dumps from those. Is there
anything else I can provide to make tracing this easier? Could we use
the addresses mentioned in the segfault messages for anything useful?
Hmm, you could try
I have a client that experienced several Out Of Memory errors a few
weeks ago (March 10 11), and I'd like to figure out the cause. In the
logs it's showing that they were getting out of memory errors for about
0.5-1 hour, after which one of the processes would crash and take the
whole
Scott Marlowe wrote:
Just because you can set max_connections to 2000 doesn't mean it's a
good idea. If your client needs 1000 persistent connections, then put
a connection pooler between your app (I'm guessing php since it
operates this way) and the database.
Running 1000 connections is a
Thanks everyone for the suggestions so far.
Tom Lane wrote:
The segfaults (sig11s) are a bit disturbing too --- what that probably
indicates is someplace using malloc() and failing to test for failure,
neither of which is a good thing. Did you by any chance get core dumps
from those? A stack
Harald Fuchs wrote:
In article [EMAIL PROTECTED],
Alex Adriaanse [EMAIL PROTECTED] writes:
Thanks for the input everyone. I think Harald's approach will work
well...
I'm not so sure anymore :-(
Consider something like that:
UPDATE tbl SET col1 = 1 WHERE col2 = 1;
UPDATE tbl SET col1 = 2
updates sent twice to the client.
Thanks again,
Alex
Harald Fuchs wrote:
In article [EMAIL PROTECTED],
Alex Adriaanse [EMAIL PROTECTED] writes:
I think that would greatly decrease the chances of a race condition
occurring, but I don't think it'd solve it. What if 150 other
revisions occur between
I think that would greatly decrease the chances of a race condition
occurring, but I don't think it'd solve it. What if 150 other revisions
occur between a row update and its corresponding commit?
Alex
Vincent Hikida wrote:
To fetch all updates since the last synchronization, the client would
Qingqing Zhou wrote:
Alex Adriaanse [EMAIL PROTECTED] writes
This seems to work, except there exists a race condition. Consider the
following series of events (in chronological order):
1. Initially, in the codes table there's a row with id=1, revision=1,
and a row with id=2, revision=2
[I've tried to send this message to pgsql-general several times now,
but even though I'm subscribed to it I never saw the message show up
in the mailing list, so I'm trying to send it from a different account
now. If you get several copies of this message, I apologize.]
I'm working on an
I'm working on an application where we have a central database server
and a bunch of clients that are disconnected most of the time, need to
maintain a local copy of the central database. The client databases are
based on One$DB since it has to be lightweight. The client does not
access the
Hi,
I'm working on an application for a client that uses PostgreSQL as its
database backend. The client wants to train their team on PostgreSQL so
that they can maintain the application and the database themselves after
it goes live should they need to. As far as I know the majority of them
11 matches
Mail list logo
