On Fri, 2016-07-29 at 12:15 -0400, Tom Lane wrote:
> rob stone writes:
> > So, could somebody tell me if the 9.6beta1 version of initdb
> > contained
> > an incorrect version constant?
>
> It did, see
>
> https://git.postgresql.org/gitweb/?p=postgresql.git=commitdiff=99
>
This has been resolved.
cheers
On Sun, Jul 31, 2016 at 6:11 PM, Patrick B wrote:
>
> CHKPOINT=$(find $ARCHIVEDIR -type f -mtime +30 -name '00*' -printf '%f\n'
> | sort -r | head -1)
>
> /usr/pgsql-${PG_VERSION}/bin/pg_archivecleanup $ARCHIVEDIR $CHKPOINT
>
>
>
​While I'm a bit suspect of this entire
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
Hi all,
I want to hold the wal_files for 30 days on my slaves.
For that reason, I created a script to do that:
*pg_archivecleaup_mv.bash:*
#!/bin/bash -eu
declare -r -x PATH='/usr/local/bin:/usr/bin:/bin';
# We just wanna delete the wal_files older than 30 days
> 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 in production
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 2016 15:26:42
> 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 Richter wrote:
> > Dear community,
> >
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