Michael H writes:
> 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;
It's unlikely that you can change the process's ulimit with just a
reload.
Hi Tom,
I've ran systemctl damon-reload; systemctl restart postgresql-9.4 and
also tried rebooting. none of these options are working.
Michael
On 17/08/15 14:47, Tom Lane wrote:
Michael H writes:
I've tried the instructions at this URL:
https://ma.ttias.be/increase-open-files-limit-in-mari
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 r
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
> 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.
>>> I've edited the /etc/security/limits.conf and added
>>> * softstack 12288
>>> * hardstack 12288
>> on a CentOS 6.7 box I can confirm that adding those lines to
>> /etc/security/limits.conf DOES increase the limit to 12288
>> (after a reboot).
>>
>> I don
Hi Chris,
On 14/08/15 17:19, Chris Mair wrote:
Hi All,
I'm tuning up my database and need to increase the max_stack_depth
parameter in postgresql.conf.
I've edited the /etc/security/limits.conf and added
* softstack 12288
* hardstack 12288
but I noticed
> Hi All,
>
> I'm tuning up my database and need to increase the max_stack_depth
> parameter in postgresql.conf.
>
> I've edited the /etc/security/limits.conf and added
> * softstack 12288
> * hardstack 12288
>
> but I noticed the comments at the top of th
Hi All,
I'm tuning up my database and need to increase the max_stack_depth
parameter in postgresql.conf.
I've edited the /etc/security/limits.conf and added
* softstack 12288
* hardstack 12288
but I noticed the comments at the top of the file -
#This fi
Cc: pgsql
Sent: Thu, March 31, 2011 6:41:27 PM
Subject: Re: [GENERAL] stack depth limit exceeded
salah jubeh writes:
> Hello,
>
> I have written this function which is simply returns the entities which
> depends
>on a certain entity. It works fine if the
> dependency tree is not
salah jubeh writes:
> Hello,
>
> I have written this function which is simply returns the entities which
> depends on a certain entity. It works fine if the
> dependency tree is not long. However, If I have an entity which are linked to
> many other entities I get
>
> stack depth limit exceeded
If you are working with Postgres version >= 8.4, you should look at the WITH
RECURSIVE (called recursive CTEs) feature:
http://www.postgresql.org/docs/8.4/static/queries-with.html
Regards,
On Thu, Mar 31, 2011 at 12:19 PM, salah jubeh wrote:
>
>
> Hello,
>
> I have written this function which
Hello,
I have written this function which is simply returns the entities which depends
on a certain entity. It works fine if the dependency tree is not long. However,
If I have an entity which are linked to many other entities I get
stack depth limit exceeded
HINT: Increase the configurat
On 5 September 2010 10:13, Ovid wrote:
> I'm getting the following error from Postgres:
>
> ERROR: stack depth limit exceeded
> HINT: Increase the configuration parameter "max_stack_depth", after ensuring
> the platform's stack depth limit is adequate.
> CONTEXT: SQL statement "UPDATE _test_
I'm getting the following error from Postgres:
ERROR: stack depth limit exceeded
HINT: Increase the configuration parameter "max_stack_depth", after ensuring
the platform's stack depth limit is adequate.
CONTEXT: SQL statement "UPDATE _test_changed_table SET updates = updates + 1
WHERE
"Bricklen Anderson" <[EMAIL PROTECTED]>; "Postgresql"
Sent: Wednesday, February 01, 2006 5:22 PM
Subject: Re: [GENERAL] Stack Depth
On Wed, Feb 01, 2006 at 05:04:22PM -0800, Bob Pawley wrote:
I do think I have a recursive problem. It's just hard to see at the
On Wed, Feb 01, 2006 at 05:04:22PM -0800, Bob Pawley wrote:
> I do think I have a recursive problem. It's just hard to see at the moment.
RAISE is your friend. If you can't figure out where the recursion
is coming from then add debugging output to the trigger functions
to see what gets called whe
ED]>; "Postgresql"
Sent: Wednesday, February 01, 2006 4:52 PM
Subject: Re: [GENERAL] Stack Depth
On Wed, Feb 01, 2006 at 03:48:38PM -0800, Bricklen Anderson wrote:
Bob Pawley wrote:
>I understand the default stack depth is about 2 meg. How do I determine
>what the stack depth
On Wed, Feb 01, 2006 at 03:48:38PM -0800, Bricklen Anderson wrote:
> Bob Pawley wrote:
> >I understand the default stack depth is about 2 meg. How do I determine
> >what the stack depth should be so that I avoid this error?
>
> check max_stack_depth in your postgresql.conf file
Before mucking wi
Bob Pawley wrote:
Hi Folks
I have three triggers and associated functions that fire on one insert
and moves row ID information to five different tables..
I am getting an error message "stack depth limit exceeded".
[snip]
You've almost certainly got a recursive trigger in there. The def
Bob Pawley wrote:
Hi Folks
I have three triggers and associated functions that fire on one insert
and moves row ID information to five different tables..
I am getting an error message "stack depth limit exceeded".
Is this normal for, what I consider, a small amount of information transfer?
Hi Folks
I have three triggers and associated functions
that fire on one insert and moves row ID information to five different
tables..
I am getting an error message "stack depth limit
exceeded".
Is this normal for, what I consider, a small amount
of information transfer?
If so, how
On Mon, Aug 29, 2005 at 01:45:32PM +1000, Jamie Deppeler wrote:
>
> CREATE TRIGGER "updateContact" AFTER INSERT OR UPDATE
> ON FOR EACH ROW
> EXECUTE PROCEDURE "contacts"."addContactField"();
Please show the actual commands that you're running; the above fails
with a syntax error because it's mis
I think that you forgot the table name.
CREATE TRIGGER "updateContact" AFTER INSERT OR UPDATE
ON contacts FOR EACH ROW
EXECUTE PROCEDURE "contacts"."addContactField"();
Frank
Jamie Deppeler wrote:
What i am trying to do is update the field contact with field values
in firstname and lastname
What i am trying to do is update the field contact with field values in
firstname and lastname
Trigger
CREATE TRIGGER "updateContact" AFTER INSERT OR UPDATE
ON FOR EACH ROW
EXECUTE PROCEDURE "contacts"."addContactField"();
Procedure
CREATE OR REPLACE FUNCTION "contacts"."addContactField" ()
Jamie Deppeler <[EMAIL PROTECTED]> writes:
> At the moment i am trying to execute a very simple function but i am
> getting the following error stack depth limit exceeded
You didn't really show the complete context, but seeing that this is a
trigger and it's trying to do an "UPDATE person" intern
On Mon, Aug 29, 2005 at 12:01:59PM +1000, Jamie Deppeler wrote:
> At the moment i am trying to execute a very simple function but i am
> getting the following error stack depth limit exceeded
That's often a sign of infinite recursion, i.e., a function that
keeps calling itself, either directly or
At the moment i am trying to execute a very simple function but i am
getting the following error stack depth limit exceeded
function
CREATE OR REPLACE FUNCTION "contacts"."addContactField" () RETURNS
trigger AS
$body$
begin
update contacts.person
set "contact" = new.firstname
where person.
28 matches
Mail list logo
