RE: Temporary tables prevent autovacuum, leading to XID wraparound

From: Robert Haas [mailto:robertmhaas(at)gmail(dot)com]
> I think we should consider having backends try to remove their temporary
> schema on startup; then, if a temp table in a backend is old enough that
> it's due for vacuum for wraparound, have autovacuum kill the connection.
> The former is necessary to prevent sessions from being killed on account
> of temp tables they "inherited" from a backend that didn't exit cleanly.

That seems to be the only reasonable solution. One might feel it annoying to emit WAL during connection establishment to delete the temp schema, but even now the client authentication can emit WAL for hot pruning while scanning pg_database, pg_authid, etc. Thanks.

> The in-place update idea won't work for a couple of reasons. First, a
> command shouldn't see the results of modifications made earlier in the same
> command. Second, using cursors, it's possible to have more than one
> distinct snapshot open against a temporary table at the same time.

You're right. And if the transaction rolls back, it needs to see the old tuples, which requires undo log.

Regards
Takayuki Tsunakawa