> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi there,
>
> I was wondering if it is a bug or a feature. When I change a key on a
> referenced table, and there is a foreign key deferred constraint, it
> triggers imediately, not at the end of transaction.
>
> If I change the reference first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I was wondering if it is a bug or a feature. When I change a key on a
referenced table, and there is a foreign key deferred constraint, it
triggers imediately, not at the end of transaction.
If I change the reference first, it works as expe
* Bruce Momjian wrote:
> Yes, please --- the patch is at:
>
> http://archives.postgresql.org/pgsql-patches/2005-06/msg00486.php
Thanks.
I've applied the patch now, and I'll keep you posted.
Best regards,
Karsten Desler
---(end of broadcast)
The following bug has been logged online:
Bug reference: 1739
Logged by: Jean-Max Reymond
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux Ubuntu
Description:memory leak in pl/perl with spi_exec_query
Details:
whith this code 1, pos
On Tue, Jun 28, 2005 at 07:03:06PM +0200, Andreas Pflug wrote:
>
> "3";"12";"0";"7 days
>
> is the result I'm getting in pgadmin.
Same here in psql:
id | seconds | accumulate | period
+-++
3 | 12 | 0 | 7 days
(1 row)
Borislav, apparently somethi
