On Fri, Nov 20, 2009 at 6:44 PM, Alain Baeckeroot
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5205
> Logged by: Alain Baeckeroot
> Email address: alain.baecker...@laposte.net
> PostgreSQL version: 8.4.1
> Operating system: Linux (Ubuntu 9.10)
> Desc
On Fri, Nov 20, 2009 at 9:58 AM, Marcel Wieland
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5202
> Logged by: Marcel Wieland
> Email address: marcel.wiel...@fondsnet.de
> PostgreSQL version: 8.2
> Operating system: Linux
> Description: Rule a
On Fri, Nov 20, 2009 at 10:11 AM, Marcel Wieland
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5203
> Logged by: Marcel Wieland
> Email address: marcel.wiel...@fondsnet.de
> PostgreSQL version: 8.2
> Operating system: Linux
> Description: Rule
Heikki Linnakangas writes:
> On all versions starting from 8.0 where subtransactions were introduced,
> this causes an assertion failure:
Ugh :-(
This ties into the more general issue that it's not clear what effect a
subtransaction rollback should have on a cursor. You could argue that
ideally
On all versions starting from 8.0 where subtransactions were introduced,
this causes an assertion failure:
postgres=# BEGIN;
BEGIN
postgres=# DECLARE foocur CURSOR FOR SELECT a FROM
generate_series(1,50) a;
DECLARE CURSOR
postgres=# SAVEPOINT sp;
SAVEPOINT
postgres=# FETCH foocur;
a
───
1
(1
