From: | "Alex Hunsaker" <badalex(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: 8.3.0 backend segfaults |
Date: | 2008-03-12 05:11:10 |
Message-ID: | 34d269d40803112211y468ee660k286af70e75a30a70@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Mar 11, 2008 at 10:59 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
> > Problem: Apparently random segfaults apparently query agnostic, seem
> > to be more frequent when a pg_dump is running
>
> Hmm, seems from the backtrace that we're trying to do a replan with an
> invalid ActiveSnapshot. What sequence of operations is the connected
> client performing, exactly? (I'm not worried about the details of the
> SQL per se, but of how it's preparing/issuing queries.)
>
> regards, tom lane
>
Its through perl-dbi using ->prepare, ->execute.. is that what you
mean? Also this is with mod_perl and Apache::DBI.
So a typical transacion looks like
connect to postgres;
begin;
do stuff here;
commit or rollback;
(next page load)
begin;
....
so potentially a database connection/session is reused on the next
page load if that makes a difference.
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2008-03-12 05:45:47 | Re: 8.3.0 backend segfaults |
Previous Message | Tom Lane | 2008-03-12 04:59:12 | Re: 8.3.0 backend segfaults |