pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedQuestion about pg_xlog
3+ messages / 3 participants
[nested] [flat]
* Question about pg_xlog
@ 2017-04-18 14:36 M Kiesewetter <mskiesewetter@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: M Kiesewetter @ 2017-04-18 14:36 UTC (permalink / raw)
To: pgsql-admin
Hi everyone,
I'm new to Postgresql and have a test environment with Postgresql 9.4.5
running on Linux.
Today I noticed that the pg_xlog was filled up to 18 Gb.
I have:
- wal_level=hot_standby
- wal_keep_segments = 100
- hot_standby = on
archive_mode = on
It's a test environment en I did a pg_resetxlogs() on the 6th of April.
I know that I shouldn't use this, and that it's only a last resort.
When I look in de pg_xlog directory I see xlog files that are kept sinds
that time.
When i look at the archive_status directory I see that all of the files
have the suffix of .done.
All the other xlogs from the time before the resetlogs are cleaned up as I
expected.
But I don't understand why the other xlogs aren't recycled.
I am looking for ways to find out why my pg_xlog is filling up.
- I checked the alertlog of the postgresql instance --> no errors
- I checked the WAL file location to see if the xlogs are being archived
--> they are present
Are there more ways to find out why my pg_xlog is filling up?
Is the pg_resetxlogs the reason why the older xlogs are not recycled?
I Hope that someone can help me.
Thanks in advance.
Regards,
Mariane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Question about pg_xlog
@ 2017-04-18 15:05 Jerry Sievers <jerry.sievers@comcast.net>
parent: M Kiesewetter <mskiesewetter@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Jerry Sievers @ 2017-04-18 15:05 UTC (permalink / raw)
To: M Kiesewetter <mskiesewetter@gmail.com>; +Cc: pgsql-admin
M Kiesewetter <mskiesewetter@gmail.com> writes:
> Hi everyone,
>
> I'm new to Postgresql and have a test environment with Postgresql
> 9.4.5 running on Linux.
> Today I noticed that the pg_xlog was filled up to 18 Gb.
> I have:
> - wal_level=hot_standby
> - wal_keep_segments = 100
> - hot_standby = on
> archive_mode = on
>
> It's a test environment en I did a pg_resetxlogs() on the 6th of
> April.
> I know that I shouldn't use this, and that it's only a last resort.
> When I look in de pg_xlog directory I see xlog files that are kept
> sinds that time.
> When i look at the archive_status directory I see that all of the
> files have the suffix of .done.
> All the other xlogs from the time before the resetlogs are cleaned up
> as I expected.
> But I don't understand why the other xlogs aren't recycled.
I'd start by looking for dormant replication slots.
select * from pg_replication_slots;
HTH
> I am looking for ways to find out why my pg_xlog is filling up.
> - I checked the alertlog of the postgresql instance --> no errors
> - I checked the WAL file location to see if the xlogs are being
> archived --> they are present
>
> Are there more ways to find out why my pg_xlog is filling up?
> Is the pg_resetxlogs the reason why the older xlogs are not recycled?
>
> I Hope that someone can help me.
> Thanks in advance.
> Regards,
> Mariane
>
>
>
--
Jerry Sievers
e: jerry.sievers@comcast.net
p: 312.241.7800
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Question about pg_xlog
@ 2017-04-19 08:12 Albe Laurenz <laurenz.albe@wien.gv.at>
parent: Jerry Sievers <jerry.sievers@comcast.net>
0 siblings, 0 replies; 3+ messages in thread
From: Albe Laurenz @ 2017-04-19 08:12 UTC (permalink / raw)
To: 'Jerry Sievers *EXTERN*' <jerry.sievers@comcast.net>; M Kiesewetter <mskiesewetter@gmail.com>; +Cc: pgsql-admin
Jerry Sievers wrote:
> M Kiesewetter <mskiesewetter@gmail.com> writes:
> > I'm new to Postgresql and have a test environment with Postgresql
> > 9.4.5 running on Linux.
> > Today I noticed that the pg_xlog was filled up to 18 Gb.
> > I have:
> > - wal_level=hot_standby
> > - wal_keep_segments = 100
> > - hot_standby = on
> > archive_mode = on
> >
> > It's a test environment en I did a pg_resetxlogs() on the 6th of
> > April.
> > I know that I shouldn't use this, and that it's only a last resort.
> > When I look in de pg_xlog directory I see xlog files that are kept
> > sinds that time.
> > When i look at the archive_status directory I see that all of the
> > files have the suffix of .done.
> > All the other xlogs from the time before the resetlogs are cleaned up
> > as I expected.
> > But I don't understand why the other xlogs aren't recycled.
>
> I'd start by looking for dormant replication slots.
>
> select * from pg_replication_slots;
Don't forget to check pg_prepared_xacts if there are any prepared
transactions that have not been committed or rolled back.
Also, if archive_mode is on, check if archive_command might have
had a non-zero return code. You should find messages in the PostgreSQL log.
Yours,
Laurenz Albe
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-04-19 08:12 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-04-18 14:36 Question about pg_xlog M Kiesewetter <mskiesewetter@gmail.com>
2017-04-18 15:05 ` Jerry Sievers <jerry.sievers@comcast.net>
2017-04-19 08:12 ` Albe Laurenz <laurenz.albe@wien.gv.at>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox