Just out of interest,
Am I able to use more than 8MB stack depth for postgresql? it's
continually warning me in /var/log/messages that I cannot exceed the
maximum of 7680kB...
is this a fixed maximum imposed by postgresql? or does postgresql find
it's maximum from system parameters and just report that number back?
attempting to adjust systemd LimitSTACK parameter for the service is
proving more difficult than anticipated.
thanks
Michael
On 17/08/15 09:16, Michael H wrote:
a little update,
I've tried the instructions at this URL:
https://ma.ttias.be/increase-open-files-limit-in-mariadb-on-centos-7-with-systemd/
I either get the same errors appear when I run systemctl daemon-reload;
systemctl restart postgresql-9.4
Aug 17 09:08:49 db1 pg_ctl[3343]: < 2015-08-17 09:08:49.305 BST >LOG:
invalid value for parameter "max_stack_depth": 10240
Aug 17 09:08:49 db1 pg_ctl[3343]: < 2015-08-17 09:08:49.305 BST >DETAIL:
"max_stack_depth" must not exceed 7680kB.
Aug 17 09:08:49 db1 pg_ctl[3343]: < 2015-08-17 09:08:49.305 BST >HINT:
Increase the platform's stack depth limit via "ulimit -s" or local
equivalent.
Aug 17 08:23:58 db1 pg_ctl[16839]: < 2015-08-17 08:23:58.533 BST >LOG:
invalid value for parameter "max_stack_depth": 10240
Aug 17 08:23:58 db1 pg_ctl[16839]: < 2015-08-17 08:23:58.533 BST
>DETAIL: "max_stack_depth" must not exceed 7680kB.
Or
I have tried moving the 'LimitSTACK=12288' to other sections of the
service file, I see this in /var/log/messages
Aug 17 08:38:47 db1 systemd: Reloading.
Aug 17 08:38:47 db1 systemd:
[/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue
'RemoveOnStop' in section 'Socket'
Aug 17 08:38:47 db1 systemd:
[/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue
'RemoveOnStop' in section 'Socket'
Aug 17 08:38:49 db1 systemd: Starting PostgreSQL 9.4 database server...
Aug 17 08:38:49 db1 kernel: postgresql94-ch[3021]: segfault at
7ffcd1a28f30 ip 00007f116054c79e sp 00007ffcd1a28f30 error 6 in
libc-2.17.so[7f1160458000+1b6000]
Aug 17 08:38:49 db1 systemd: postgresql-9.4.service: control process
exited, code=killed status=11
Aug 17 08:38:49 db1 systemd: Failed to start PostgreSQL 9.4 database
server.
Aug 17 08:38:49 db1 systemd: Unit postgresql-9.4.service entered failed
state.
I've also tried what it says in the service file -
# It's not recommended to modify this file in-place, because it will be
# overwritten during package upgrades. If you want to customize, the
# best way is to create a file
"/etc/systemd/system/postgresql-9.4.service",
# containing
# .include /lib/systemd/system/postgresql-9.4.service
# ...make your changes here...
# For more info about custom unit files, see
#
http://fedoraproject.org/wiki/Systemd#How_do_I_customize_a_unit_file.2F_add_a_custom_unit_file.3F
But nothing works as yet!
On 17/08/15 09:04, Chris Mair wrote:
I don't know if that works, but it is in line with the
"systemd broke things" idea...
Rereading this, I realize this might come over as too harsh.
What I meant was "the introduction of systemd broke things".
So this wasn't meant as anti-systemd or anything. No flames
intented ;)
Bye,
Chris.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
