From: | Marcin Mańk <marcin(dot)mank(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: FATAL: ReleaseSavepoint: unexpected state STARTED |
Date: | 2011-08-18 07:57:52 |
Message-ID: | CAK61fk4oj+EogyRHRtBnnc5NKanYPVTgbHJxEjRmaswqLGiMNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 17, 2011 at 11:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?UTF-8?B?TWFyY2luIE1hxYRr?= <marcin(dot)mank(at)gmail(dot)com> writes:
>> psql -c 'release q; prepare q(int) as select 1'
>> FATAL: ReleaseSavepoint: unexpected state STARTED
>
> Can't get terribly excited about that, seeing that the statement is
> surely going to draw an error and abort processing the rest of the
> command string in any case ...
Oh, I thought FATAL was disconnectiong other sessions. Yeah, that was
not bad enough.
Here is a better one:
psql postgres -c 'savepoint q; select 1'
FATAL: DefineSavepoint: unexpected state STARTED
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Greetings
Marcin Mańk
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2011-08-18 09:21:44 | Re: PATCH: Compiling PostgreSQL using ActiveState Python 3.2 |
Previous Message | Ashesh Vashi | 2011-08-18 07:27:51 | Re: PATCH: Compiling PostgreSQL using ActiveState Python 3.2 |