Re: [HACKERS] backend closed the channel unexpectedly

Lists: pgsql-hackersPostg윈 토토SQL
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Wetzel <dave(at)turbocat(dot)de>
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-ports(at)postgreSQL(dot)org, gerald(at)lucky(dot)turbocat(dot)de
Subject: Re: [HACKERS] backend closed the channel unexpectedly
Date: 1999-05-12 23:15:24
Message-ID: 29508.926550924@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers Postg윈 토토SQL

David Wetzel <dave(at)turbocat(dot)de> writes:
> I have found a bug that is very easy to reprouduce here:

> [ backend crash after many attempts to insert same data into a
> uniquely-indexed table ]

This may be the same bug that was discussed earlier today on the hackers
list: the backend fails to release temporary memory after an error, so
if you make it generate enough error messages during one session you can
eventually run out of memory. Watch the process with 'top' or some such
to see if it gets up to your system's limit on process size just before
failing.

I'm hoping to look into the cause of the memory leak shortly, but
no guarantees about how soon it might be fixed ;-).

regards, tom lane


From: David Wetzel <dave(at)turbocat(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-ports(at)postgreSQL(dot)org, gerald(at)lucky(dot)turbocat(dot)de
Subject: Re: [PORTS] Re: [HACKERS] backend closed the channel unexpectedly
Date: 1999-05-12 23:41:29
Message-ID: 199905122341.BAA00340@cat.turbocat.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers 503 토토 커뮤니티

> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Sender: owner-pgsql-ports(at)postgreSQL(dot)org
>
> David Wetzel <dave(at)turbocat(dot)de> writes:
> > I have found a bug that is very easy to reprouduce here:
>
> > [ backend crash after many attempts to insert same data into a
> > uniquely-indexed table ]
>
> This may be the same bug that was discussed earlier today on the hackers

I cc'ed the mail to pgsql-hackers(at)postgreSQL(dot)org, pgsql-ports(at)postgreSQL(dot)org
But I only subscribe to pgsql-ports(at)postgreSQL(dot)org(dot)

(...)
> I'm hoping to look into the cause of the memory leak shortly, but
> no guarantees about how soon it might be fixed ;-).
>
> regards, tom lane

Great. What we did as bugfix in our importer program is to close and reopen
the connection to the backend each 1000 rows. This is very ugly but seems to
work until someone with the backend-knowlege has fixed the bug.

First we thought that we made a mistake in our EOAdaptor*) for PSQL and
debugged that beast for many hours...

Dave

*) For EOF and WebObjects from Apple/NeXT see www.turbocat.de
_ _
_(_)(_)_ David Wetzel, Turbocat's Development,
(_) __ (_) Buchhorster Strasse, D-16567 Muehlenbeck/Berlin, FRG,
_/ \_ Fax +49 33056 82835 NeXTmail dave(at)turbocat(dot)de
(______) http://www.turbocat.de/
DEVELOPMENT * CONSULTING * ADMINISTRATION