Re: [PERFORM] Big IN() clauses etc : feature proposal - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PERFORM] Big IN() clauses etc : feature proposal
Date
Msg-id 4335.1147385316@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PERFORM] Big IN() clauses etc : feature proposal  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: [PERFORM] Big IN() clauses etc : feature proposal  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> I'd hope that wasn't what's happening... is the backend smart enough to
> know not to fsync anything involved with the temp table?

The catalog entries required for it have to be fsync'd, unless you enjoy
putting your entire database at risk (a bad block in pg_class, say,
would probably take out more than one table).

It's interesting to speculate about keeping such catalog entries in
child tables of pg_class etc that are themselves temp tables.  Resolving
the apparent circularity of this is left as an exercise for the reader.

            regards, tom lane

pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Compressing table images
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [PERFORM] Big IN() clauses etc : feature proposal