Re: [HACKERS] Deferred trigger queue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <wieck(at)debis(dot)com>
Cc: PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Deferred trigger queue
Date: 2000-02-08 16:41:58
Message-ID: 2249.950028118@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

wieck(at)debis(dot)com (Jan Wieck) writes:
> looking at all the complications about dealing with segmented
> files etc., I wonder if it's really worth the efford to add
> file buffering to the trigger queue.

You shouldn't be thinking about that. Use a BufFile (see
src/include/storage/buffile.h), and you have temp file creation,
file segmentation and auto cleanup at xact abort with no more work
than fopen/fwrite would be. See nodeHash.c/nodeHashjoin.c for an
example of use.

> Of course, if someone updates millions of rows in an RI
> scenario during one transaction, it could blow away the
> backend. But I'd prefer to leave this as a well known problem
> for 7.1 and better start on creating a good regression test
> and some documentation for it.

However, if you think that there are other tasks that are higher
priority than this one, I won't argue.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-02-08 16:49:09 AW: [HACKERS] Another nasty cache problem
Previous Message Bruce Momjian 2000-02-08 16:38:53 Re: [HACKERS] psql and libpq fixes