Re: stale WAL files?

On 4/10/19 6:03 PM, Rene Romero Benavides wrote: What's your current max_wal_size parameter? SHOW max_wal_size; If it's 8GB as your configuration's previous value, you would get a constant share of 512 WAL files. If it's a development environment set it to the desired size, the smaller the

Re: stale WAL files?

What's your current max_wal_size parameter? SHOW max_wal_size; If it's 8GB as your configuration's previous value, you would get a constant share of 512 WAL files. If it's a development environment set it to the desired size, the smaller the value, the more frequent the checkpoints, but your

Re: stale WAL files?

As per your configuration : max_wal_size = 50GB this seems to be the cause for the WAL files piling up. this has been declared twice, the last one is taking effect. -- El genio es 1% inspiración y 99% transpiración. Thomas Alva Edison http://pglearn.blogspot.mx/ I've manage to generate

Re: stale WAL files?

> On Apr 3, 2019, at 5:23 PM, Rene Romero Benavides > wrote: > > > > On Wed, Apr 3, 2019 at 1:05 PM Rob Sargent > wrote: > > >> On Apr 1, 2019, at 9:20 PM, Rene Romero Benavides > > wrote: >> >> >> On Mon, Apr 1, 2019 at

Re: stale WAL files?

On Wed, Apr 3, 2019 at 1:05 PM Rob Sargent wrote: > > > On Apr 1, 2019, at 9:20 PM, Rene Romero Benavides > wrote: > > > On Mon, Apr 1, 2019 at 6:30 PM Rene Romero Benavides < > rene.romer...@gmail.com> wrote: > >> >> On Sat, Mar 30, 2019 at 5:03 PM Gmail wrote: >> >>> >>> >>> > On Mar 30,

Re: stale WAL files?

> On Apr 1, 2019, at 9:20 PM, Rene Romero Benavides > wrote: > > > On Mon, Apr 1, 2019 at 6:30 PM Rene Romero Benavides > wrote: > > On Sat, Mar 30, 2019 at 5:03 PM Gmail > wrote: > > > > On Mar 30, 2019, at 10:54 AM, Gmail

Re: stale WAL files?

Sorry folks, I’m still home nursing a nasty chest cold and my only tool today is an iPad. I have failed to get the postgresql.conf into the copy buffer so that, along with the results of pg_settings, will have to wait for another day. Today there are “only” 135 Mar 16 WAL files. I haven’t

Re: stale WAL files?

I’m under fighting a nasty cold. It may take a day or two for me to response to recent questions and suggestion.

Re: stale WAL files?

On Mon, Apr 1, 2019 at 6:30 PM Rene Romero Benavides < rene.romer...@gmail.com> wrote: > > On Sat, Mar 30, 2019 at 5:03 PM Gmail wrote: > >> >> >> > On Mar 30, 2019, at 10:54 AM, Gmail wrote: >> > >> > >> On Mar 29, 2019, at 6:58 AM, Michael Paquier >> wrote: >> >>> >> >>> On Thu, Mar 28,

Re: stale WAL files?

On Sat, Mar 30, 2019 at 5:03 PM Gmail wrote: > > > > On Mar 30, 2019, at 10:54 AM, Gmail wrote: > > > > > On Mar 29, 2019, at 6:58 AM, Michael Paquier > wrote: > >>> > >>> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: > >>> This is pg10 so it's pg_wal. ls -ltr > >>> > >>>

Re: stale WAL files?

> On Mar 30, 2019, at 10:54 AM, Gmail wrote: > > On Mar 29, 2019, at 6:58 AM, Michael Paquier wrote: >>> >>> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: >>> This is pg10 so it's pg_wal. ls -ltr >>> >>> >>> -rw---. 1 postgres postgres 16777216 Mar 16 16:33 >>>

Re: stale WAL files?

> On Mar 29, 2019, at 6:58 AM, Michael Paquier wrote: > >> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: >> This is pg10 so it's pg_wal. ls -ltr >> >> >> -rw---. 1 postgres postgres 16777216 Mar 16 16:33 >> 00010CEA00B1 >> -rw---. 1 postgres postgres

Re: stale WAL files?

> On Mar 29, 2019, at 6:58 AM, Michael Paquier wrote: > >> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: >> This is pg10 so it's pg_wal. ls -ltr >> >> >> -rw---. 1 postgres postgres 16777216 Mar 16 16:33 >> 00010CEA00B1 >> -rw---. 1 postgres postgres

Re: stale WAL files?

> On Mar 29, 2019, at 6:58 AM, Michael Paquier wrote: > >> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: >> This is pg10 so it's pg_wal. ls -ltr >> >> >> -rw---. 1 postgres postgres 16777216 Mar 16 16:33 >> 00010CEA00B1 >> -rw---. 1 postgres postgres

Re: stale WAL files?

> On Mar 29, 2019, at 6:58 AM, Michael Paquier wrote: > >> On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: >> This is pg10 so it's pg_wal. ls -ltr >> >> >> -rw---. 1 postgres postgres 16777216 Mar 16 16:33 >> 00010CEA00B1 >> -rw---. 1 postgres postgres

Re: stale WAL files?

On Thu, Mar 28, 2019 at 09:53:16AM -0600, Rob Sargent wrote: > This is pg10 so it's pg_wal.  ls -ltr > > > -rw---. 1 postgres postgres 16777216 Mar 16 16:33 > 00010CEA00B1 > -rw---. 1 postgres postgres 16777216 Mar 16 16:33 > 00010CEA00B2 > >  ... 217 more on

Re: stale WAL files?

On 3/28/19 7:30 AM, Michael Paquier wrote: On Tue, Mar 26, 2019 at 09:50:37AM -0600, Rob Sargent wrote: No, sorry I should have said that up front. We’re simple folk. What is the WAL position (LSN) postgres=# select * from pg_current_wal_flush_lsn();  pg_current_wal_flush_lsn

Re: stale WAL files?

On Tue, Mar 26, 2019 at 09:50:37AM -0600, Rob Sargent wrote: > No, sorry I should have said that up front. We’re simple folk. What is the WAL position (LSN) where Postgres is writing to and what is the set of WAL segments in pg_wal (or pg_xlog if that's a server older than 10)? Please

Re: stale WAL files?

On 3/25/19 5:10 PM, Rob Sargent wrote: PG10.7, Centos7 On Mar15 we filled our default tablespace/WAL partition.  Cleaned up some old dumps and restarted.  pg_wal had apparently exploded but cleaned itself up by the next day. On Mar16 I ran CHECKPOINT in all databases on that server (except

stale WAL files?

PG10.7, Centos7 On Mar15 we filled our default tablespace/WAL partition. Cleaned up some old dumps and restarted. pg_wal had apparently exploded but cleaned itself up by the next day. On Mar16 I ran CHECKPOINT in all databases on that server (except template0). All seems fine except for 271