On 10/4/15 6:10 PM, Tom Lane wrote:
Andrew Dunstan<and...@dunslane.net> writes:
>Sorry, I'm a bit late to this party. Does what you have committed mean
>people are less likely to see "Out of Memory" coming from
>pg_stat_statements? If not, what can be done about them short of a
>restart? And what bad effects follow from an event generating them?
The main thing we've done that will alleviate that is increase the size of
query text file that the garbage-collection routine can cope with from
MaxAllocSize (1GB) to MaxAllocHugeSize (at least 2GB, lots more on 64bit
machines, though on 32-bit you probably can't get to 2GB anyway ...).
FWIW, I've verified on $CLIENT's system that this works as Tom
described. The truncation happened somewhere a bit north of 3GB, which
seems odd as this is a 64 bit system. But at least there were no OOM errors.
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: