From: | Johannes Truschnigg <johannes(at)truschnigg(dot)info> |
---|---|
To: | Erwin Fritz <efritz(at)gljpc(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: temp_file_limit parameter ignored? |
Date: | 2018-08-20 15:23:50 |
Message-ID: | 20180820152350.h47sxqxknhnq6wpg@vault.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Aug 20, 2018 at 03:09:33PM +0000, Erwin Fritz wrote:
> 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.
Hmm. That's strange, because if you properly edited and saved that file,
postgres should at the very least notice the changed reboot value for the
setting. Are you sure you succesfully restarted/reloaded postgresql after your
change?
SELECT pg_reload_conf();
as a superuser role ("postgres" is fine) should do. Make sure to check the
postgresql logs afterwards, since it will contain information on changed
settings and syntax errors/problems (if any)!
Since you're on pg9.5, you could also use the ALTER SYSTEM command to commit
configuration changes, that will have postgres take care of applying and
persisting the changes you make. You should read
https://www.postgresql.org/docs/9.5/static/sql-altersystem.html for more info
on that particular topic/feature.
Hth.
--
with best regards:
- Johannes Truschnigg ( johannes(at)truschnigg(dot)info )
www: https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp: johannes(at)truschnigg(dot)info
Please do not bother me with HTML-email or attachments. Thank you.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-08-20 15:26:11 | Re: temp_file_limit parameter ignored? |
Previous Message | Mark Williams | 2018-08-20 15:16:24 | RE: Setting up SSL for postgre |