pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jerry Sievers <gsievers19@comcast.net>
To: Erwin Fritz <efritz@gljpc.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Johannes Truschnigg <johannes@truschnigg.info>
Cc: pgsql-admin\@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: temp_file_limit parameter ignored?
Date: Mon, 20 Aug 2018 15:44:02 -0500
Message-ID: <87k1okg44t.fsf@jsievers.enova.com> (raw)
In-Reply-To: <9E6E27BCA0E8EE478089F158D73AF936A91F367A@Exch10-Mailbox.corp.gljpc.com>
References: <9E6E27BCA0E8EE478089F158D73AF936A91EB443@Exch10-Mailbox.corp.gljpc.com>
	<20180820131535.ljrnxgph62ypus2z@vault.lan>
	<9E6E27BCA0E8EE478089F158D73AF936A91ED957@Exch10-Mailbox.corp.gljpc.com>
	<19727.1534778771@sss.pgh.pa.us>
	<9E6E27BCA0E8EE478089F158D73AF936A91F367A@Exch10-Mailbox.corp.gljpc.com>

Erwin Fritz <efritz@gljpc.com> writes:

> Here's the output:
>
> select * from pg_settings where name = 'temp_file_limit';
> -[ RECORD 1 ]---+-------------------------------------------------------------------
> name            | temp_file_limit
> setting         | 4194304
> unit            | kB
> category        | Resource Usage / Disk
> short_desc      | Limits the total size of all temporary files used by each session.
> extra_desc      | -1 means no limit.
> context         | superuser
> vartype         | integer
> source          | database

^^^^^

This means someone/thing said...

ALTER DATABASE $foodb SET temp_file_limit to '$whatever';

See psql \drds.

Just do an explicit override in your own job prior to the code that
errors out due to resource shortfall.

SET temp_file_limit to -1;

HTH


> min_val         | -1
> max_val         | 2147483647
> enumvals        |
> boot_val        | -1
> reset_val       | 4194304
> sourcefile      |
> sourceline      |
> pending_restart | f
>
>
>
>
> -----------------------------
> This message is intended only for the recipient(s) to which it is
> addressed and may contain information that is privileged and
> confidential. If you have received this message in error, please
> notify the sender immediately and delete all copies.
> -----------------------------
>
> ________________________________________
> From: Tom Lane [tgl@sss.pgh.pa.us]
> Sent: August 20, 2018 09:26
> To: Erwin Fritz
> Cc: Johannes Truschnigg; pgsql-admin@postgresql.org
> Subject: Re: temp_file_limit parameter ignored?
>
> Erwin Fritz <efritz@gljpc.com> writes:
>> Hmm. I did that, and the sourcefile and sourceline values are blank. I then ran "show config_file" and the result has the correct location of the file.
>
> What does the "source" column say?
>
>                         regards, tom lane
>
>

-- 
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800




view thread (10+ messages)  latest in thread

Message-ID: <87k1okg44t.fsf@jsievers.enova.com>
Permalink:  ../87k1okg44t.fsf@jsievers.enova.com/
Also on:    postgresql.org/message-id/87k1okg44t.fsf@jsievers.enova.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gsievers19@comcast.net, efritz@gljpc.com, tgl@sss.pgh.pa.us, johannes@truschnigg.info
  Subject: Re: temp_file_limit parameter ignored?
  In-Reply-To: <87k1okg44t.fsf@jsievers.enova.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox