From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
---|---|
To: | "" <wizard580(at)gmail(dot)com> <wizard580(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2491: Database crash and restart |
Date: | 2006-06-28 00:39:11 |
Message-ID: | 8E8B2528-CD0B-49D6-A303-1058E4E64A66@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Without a core dump or a repeatable test case, there's not really
anything we can do to help you here.
On Jun 23, 2006, at 12:42 AM, "" <wizard580(at)gmail(dot)com>
<wizard580(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2491
> Logged by:
> Email address: wizard580(at)gmail(dot)com
> PostgreSQL version: 8.1.4
> Operating system: Debian sid unstable
> Description: Database crash and restart
> Details:
>
> Situation:
> I have running transaction which makes a frequently calls to a pl/
> pgSQL
> functions via several triggers. All in one transaction. Transaction
> running
> for a 30 sec - 1 min time longs. Then I have a file with this
> functions.
> CREATE OR REPLACE FUNCTION ........
> I made this: cat <my_file> | psql <base> -U postgres
>
> SQL server crashed.
> When no transaction active, all fine.
> I can not wait a transaction to finish, because it may begin again
> immediately, and again, and again. Untill "system" decided to make
> some
> waiting for a some event.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-06-28 00:41:19 | Re: BUG #2492: "unexpected EOF on client connection" message in log |
Previous Message | Tom Lane | 2006-06-27 22:21:01 | Re: Bug#372115: Last security update of postgresql-contrib breaks database replication with DBMirror.pl |