| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Dmitry Samersoff <dms(at)wplus(dot)net>, pgsql-hackers(at)postgreSQL(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: [HACKERS] PID of backend |
| Date: | 1999-06-02 19:14:23 |
| Message-ID: | 25755.928350863@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
>> I need to restart backend because (as written above)
>> every 300 000 "open cursor" query completly loose it's mind.
> I hope 6.5 due on June 7 will fix your problems.
It might. Looking back at the original gripe, I notice it mentions
doing rollbacks:
>>>>> Jun 2 00:12:32 mail popper[17585]: PgSQL:ROLLBACK failed:
If Dmitry is doing a whole lot of rollbacks, he might be running into
that aborted-transactions-leak-memory bug that we fixed a few weeks ago.
Meanwhile, I still say that getting rid of a backend via kill() is a
dangerous and unnecessary "recovery" mechanism. What's wrong with
just closing and reopening the connection instead?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nat Howard | 1999-06-02 19:23:38 | RE: [HACKERS] Re: [SQL] Column name's length |
| Previous Message | Brent Waldrop | 1999-06-02 19:05:15 | XOpenDisplay problems? |