DISCARD ALL (Again) - Mailing list pgsql-hackers

From Joshua D. Drake
Subject DISCARD ALL (Again)
Date
Msg-id 53503D25.3010107@commandprompt.com
Whole thread Raw
Responses Re: DISCARD ALL (Again)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: DISCARD ALL (Again)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Hello,

Over at my quaint establishment we have been working on some plython 
work that makes use of GD. We wrote this code with the assumption (per 
the docs) that when you issued a DISCARD ALL, the GD would be cleared. 
Apparently this is not the case. The docs themselves are clearly wrong, 
and this has been brought up before multiple times (that DISCARD ALL 
doesn't do what people think it does).

Does it seem reasonable based on the docs:

DISCARD ALL:

Releases all temporary resources associated with the current session and 
resets the session to its initial state.

That we should also release the GD?

Sincerely,

Joshua D. Drake


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
Political Correctness is for cowards.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: assertion in 9.4 with wal_level=logical
Next
From: Peter Geoghegan
Date:
Subject: Re: Clock sweep not caching enough B-Tree leaf pages?