Is this a TODO or is it going to be fixed for 8.2?
---
Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Yeah, I think there are a few possibilities around truncate inside a
> > savepoint that's rolledback that
On Mon, 21 Aug 2006, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Yeah, I think there are a few possibilities around truncate inside a
> > savepoint that's rolledback that we have to be careful of.
>
> Yuck :-(
>
> > If we could mark the entries in some way so we knew whether o
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Yeah, I think there are a few possibilities around truncate inside a
> savepoint that's rolledback that we have to be careful of.
Yuck :-(
> If we could mark the entries in some way so we knew whether or not they
> were made obsolete by a truncate of ou
On Mon, 21 Aug 2006, Tom Lane wrote:
> Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> > CREATE TABLE category (
> > id INT PRIMARY KEY,
> > name TEXT);
>
> > CREATE TABLE category_todo (
> > cat_id INT REFERENCES category(id)
> > DEFERRABLE INITIALLY DEFERRED
> > );
>
>
Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> CREATE TABLE category (
> id INT PRIMARY KEY,
> name TEXT);
> CREATE TABLE category_todo (
> cat_id INT REFERENCES category(id)
> DEFERRABLE INITIALLY DEFERRED
> );
> BEGIN;
> INSERT INTO category (id, name) VALUES (0, 'te
Hello Tom,
in June I've complained about a 'failed to fetch new tuple for AFTER
trigger' error and you requested a test case here:
http://archives.postgresql.org/pgsql-general/2006-07/msg00855.php
I finally got around to strip down the problem. The error first occurred
to me using a 8.2devel
