Hello
On 08/01/2016 12:15 AM, Tom Lane wrote:
Edson Richter writes:
From: t...@sss.pgh.pa.us
Uh, doesn't the CONTEXT field of error messages give you that already?
Would you give me an example where I can get the info you mention above? Do I
need to enable some kind of parameter to get thi
Edson Richter writes:
>> From: t...@sss.pgh.pa.us
>> Uh, doesn't the CONTEXT field of error messages give you that already?
> Would you give me an example where I can get the info you mention above? Do I
> need to enable some kind of parameter to get this context field?
Well, you have not menti
> From: t...@sss.pgh.pa.us
> To: edsonrich...@hotmail.com
> CC: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Proposal "stack trace" like debugging option in
> PostgreSQL
> Date: Sun, 31 Jul 2016 11:56:11 -0400
>
> Edson Richter writes:
> > But
On 07/31/2016 01:27 PM, Edson Richter wrote:
Please reply to list also
Ccing list.
Subject: Re: [GENERAL] Proposal "stack trace" like debugging option in
PostgreSQL
To: edsonrich...@hotmail.com; pgsql-general@postgresql.org
From: adrian.kla...@aklaver.com
Date: Sat, 30 Jul 201
> Subject: Re: [GENERAL] Proposal "stack trace" like debugging option in
> PostgreSQL
> To: edsonrich...@hotmail.com; pgsql-general@postgresql.org
> From: adrian.kla...@aklaver.com
> Date: Sat, 30 Jul 2016 15:26:42 -0700
>
> On 07/30/2016 10:52 AM, Edson Ri
Edson Richter writes:
> But in production this is not possible, and I would to propose a feature
> that has less impact over production then a debug extension: a
> stacktrace of calls.
> Simular to Java stack traces, but disabled by default. When enabled, In
> case of an event like "duplicate
On 07/30/2016 10:52 AM, Edson Richter wrote:
Dear community,
Sorry if this is not the right place for proposing new features. Also,
sorry if I'm proposing something already existing.
I do currently use the "debug" extension to better understand the
entrophy of my application regarding database
Dear community,
Sorry if this is not the right place for proposing new features. Also,
sorry if I'm proposing something already existing.
I do currently use the "debug" extension to better understand the
entrophy of my application regarding database.
But in production this is not possible,
