public inbox for [email protected]
help / color / mirror / Atom feedInvalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
7+ messages / 3 participants
[nested] [flat]
* Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
@ 2017-06-09 13:55 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Cocco Gianfranco @ 2017-06-09 13:55 UTC (permalink / raw)
To: pgsql-performance; [email protected] <[email protected]>; +Cc: DBA <[email protected]>
Hi,
We have a big problem with managing the number of WAL products, during database activity, so I would try to write to you.
With pg_rman utility, we can't save thousands of WAL files every few hours, to be used for a possible recovery.
We are using a production environment 9.2 PostgreSQL server which processes a database of about 260 GB
Is there a way to fix "wal_segsize" to about 1 Gb in 9.2. version, and "rebuild" postgreSQL server?
The goal is to drastically reduce the number of WALs.
Upgrading to 9.5, is the only way to fix this issue?
Thank you.
[Descrizione: cid:[email protected]]
_______________________________
Gianfranco Cocco
Gruppo DBA Torino
Managed Operations - Data Center Factory
[email protected]<mailto:[email protected]>
Engineering.MO S.p.A
Corso Mortara, 22 - 10149 Torino
Tel. 011 19449548 (SHORT CODE: 676548)
www.eng.it<http://www.eng.it;
___________________________
Attachments:
[image/jpeg] image001.jpg (4.0K, 3-image001.jpg)
download | view image
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
@ 2017-06-09 22:43 ` Michael Paquier <[email protected]>
2017-06-12 17:27 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Jeff Janes <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Michael Paquier @ 2017-06-09 22:43 UTC (permalink / raw)
To: Cocco Gianfranco <[email protected]>; +Cc: pgsql-performance; [email protected] <[email protected]>; DBA <[email protected]>
On Fri, Jun 9, 2017 at 10:55 PM, Cocco Gianfranco
<[email protected]> wrote:
> Is there a way to fix “wal_segsize” to about 1 Gb in 9.2. version, and “rebuild” postgreSQL server?
As long as you are able to compile your own version of Postgres and
your distribution does not allow that, there is nothing preventing you
to do so.
> The goal is to drastically reduce the number of WALs.
> Upgrading to 9.5, is the only way to fix this issue?
Note that a server initialized with a segment size of X won't work
with a binary compiled with a size of Y. But you can always take a
logical dump of the server before the upgrade, and reload it in the
version of the server with a larger segment size. The cost here is
more downtime.
--
Michael
--
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
@ 2017-06-12 17:27 ` Jeff Janes <[email protected]>
2017-06-12 21:25 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Jeff Janes @ 2017-06-12 17:27 UTC (permalink / raw)
To: Michael Paquier <[email protected]>; +Cc: Cocco Gianfranco <[email protected]>; pgsql-performance; [email protected] <[email protected]>; DBA <[email protected]>
On Fri, Jun 9, 2017 at 3:43 PM, Michael Paquier <[email protected]>
wrote:
> On Fri, Jun 9, 2017 at 10:55 PM, Cocco Gianfranco
> <[email protected]> wrote:
> > Is there a way to fix “wal_segsize” to about 1 Gb in 9.2. version, and
> “rebuild” postgreSQL server?
>
> As long as you are able to compile your own version of Postgres and
> your distribution does not allow that, there is nothing preventing you
> to do so.
>
But there is something preventing it. wal_segsize cannot exceed 64MB in
9.2. v10 will be the first version which will allow sizes above 64MB.
Cheers,
Jeff
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
2017-06-12 17:27 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Jeff Janes <[email protected]>
@ 2017-06-12 21:25 ` Michael Paquier <[email protected]>
2017-06-13 09:10 ` R: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Michael Paquier @ 2017-06-12 21:25 UTC (permalink / raw)
To: Jeff Janes <[email protected]>; +Cc: Cocco Gianfranco <[email protected]>; pgsql-performance; [email protected] <[email protected]>; DBA <[email protected]>
On Tue, Jun 13, 2017 at 2:27 AM, Jeff Janes <[email protected]> wrote:
> But there is something preventing it. wal_segsize cannot exceed 64MB in
> 9.2. v10 will be the first version which will allow sizes above 64MB.
Yes, indeed. I have misread --with-segsize and --with-wal-segsize in
the docs. Sorry for the confusion.
--
Michael
--
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
^ permalink raw reply [nested|flat] 7+ messages in thread
* R: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
2017-06-12 17:27 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Jeff Janes <[email protected]>
2017-06-12 21:25 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
@ 2017-06-13 09:10 ` Cocco Gianfranco <[email protected]>
2017-06-13 09:34 ` Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Cocco Gianfranco @ 2017-06-13 09:10 UTC (permalink / raw)
To: Michael Paquier <[email protected]>; Jeff Janes <[email protected]>; +Cc: pgsql-performance; [email protected] <[email protected]>; DBA <[email protected]>
Thank you.
If I understand it well, we can build a new postgreSQL server, by setting this value into "configure" file?
--with-wal-segsize=SEGSIZE becomes --with-wal-segsize=1024 ??
_______________________________
Gianfranco Cocco
Gruppo DBA Torino
Managed Operations - Data Center Factory
[email protected]
Engineering.MO S.p.A
Corso Mortara, 22 - 10149 Torino
Tel. 011 19449548 (SHORT CODE: 676548)
www.eng.it
___________________________
-----Messaggio originale-----
Da: Michael Paquier [mailto:[email protected]]
Inviato: lunedì 12 giugno 2017 23:26
A: Jeff Janes <[email protected]>
Cc: Cocco Gianfranco <[email protected]>; [email protected]; [email protected]; DBA <[email protected]>
Oggetto: Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
On Tue, Jun 13, 2017 at 2:27 AM, Jeff Janes <[email protected]<mailto:[email protected]>> wrote:
> But there is something preventing it. wal_segsize cannot exceed 64MB
> in 9.2. v10 will be the first version which will allow sizes above 64MB.
Yes, indeed. I have misread --with-segsize and --with-wal-segsize in the docs. Sorry for the confusion.
--
Michael
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
2017-06-12 17:27 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Jeff Janes <[email protected]>
2017-06-12 21:25 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
2017-06-13 09:10 ` R: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
@ 2017-06-13 09:34 ` Michael Paquier <[email protected]>
2017-06-13 20:38 ` Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Michael Paquier @ 2017-06-13 09:34 UTC (permalink / raw)
To: Cocco Gianfranco <[email protected]>; +Cc: Jeff Janes <[email protected]>; pgsql-performance; [email protected] <[email protected]>; DBA <[email protected]>
On Tue, Jun 13, 2017 at 6:10 PM, Cocco Gianfranco
<[email protected]> wrote:
> If I understand it well, we can build a new postgreSQL server, by setting
> this value into "configure" file?
>
> --with-wal-segsize=SEGSIZE becomes --with-wal-segsize=1024 ??
Yes, but as Jeff has pointed out upthread, this value can just go up
to 64 when using 9.5.
--
Michael
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
2017-06-12 17:27 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Jeff Janes <[email protected]>
2017-06-12 21:25 ` Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
2017-06-13 09:10 ` R: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-13 09:34 ` Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Michael Paquier <[email protected]>
@ 2017-06-13 20:38 ` Michael Paquier <[email protected]>
0 siblings, 0 replies; 7+ messages in thread
From: Michael Paquier @ 2017-06-13 20:38 UTC (permalink / raw)
To: Cocco Gianfranco <[email protected]>; +Cc: Jeff Janes <[email protected]>; pgsql-performance; DBA <[email protected]>
On Tue, Jun 13, 2017 at 10:39 PM, Cocco Gianfranco
<[email protected]> wrote:
> ./configure --with-wal-segsize=1024
>
> checking for WAL segment size... configure: error: Invalid WAL segment size.
> Allowed values are 1,2,4,8,16,32,64.
>
> Please, how can I do?
When trying to compile Postgres 9.6, the maximum value is 64. If you
want to allow 1GB of WAL segment size you will need to wait for 10, or
just use 64MB.
--
Michael
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2017-06-13 20:38 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-06-09 13:55 Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-09 22:43 ` Michael Paquier <[email protected]>
2017-06-12 17:27 ` Jeff Janes <[email protected]>
2017-06-12 21:25 ` Michael Paquier <[email protected]>
2017-06-13 09:10 ` R: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 Cocco Gianfranco <[email protected]>
2017-06-13 09:34 ` Michael Paquier <[email protected]>
2017-06-13 20:38 ` Michael Paquier <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox