On 12/9/15 7:05 PM, Andreas Kretschmer wrote:
I'm really newbie to PostgreSQL but the boss pushed me to handle it
>and implement it in production f*&%*$%%$#%$#&# (forgive me)
>They don't hire a database expert, I don't know why.
You can learn that. PostgreSQL is really, really great.
Btw.: i kno
> FattahRozzaq hat am 10. Dezember 2015 um 01:27
> geschrieben:
>
>
> Hi John,
>
> I really don't know why I should keep the wal archives.
That's the problem! But that's your part, not our. If you need a Backup with
PITR-capability you have to create a so called basebackup and continously W
On 12/09/2015 04:27 PM, FattahRozzaq wrote:
Hi John,
I really don't know why I should keep the wal archives.
So who set up the archiving and why?
Is archive recovery set up on the standby?:
http://www.postgresql.org/docs/9.4/interactive/archive-recovery-settings.html
I implement streaming
Hi John,
Really thanking you for spend time typing and responding my email.
I think the archive_command returns success, I can see the archive
directory piling up 16MB every 2 minutes.
Maybe the pgarchivecleanup is the solution to cleanup the contents of
archive folder?
How to properly do it?
What
On 12/9/2015 4:27 PM, FattahRozzaq wrote:
I really don't know why I should keep the wal archives.
I implement streaming replication into 1 server (standby server).
I'm really newbie to PostgreSQL but the boss pushed me to handle it
and implement it in production f*&%*$%%$#%$#&# (forgive me)
They
On 12/09/2015 04:38 PM, FattahRozzaq wrote:
Quick information,
After I realize, the line "archive_command=/bin/true" is a bad
decision, I have revert it back.
Now I'm really confused and panic.
I don't know what to do, and I don't really understand the postgresql.conf
I'm a network engineer, I s
Quick information,
After I realize, the line "archive_command=/bin/true" is a bad
decision, I have revert it back.
Now I'm really confused and panic.
I don't know what to do, and I don't really understand the postgresql.conf
I'm a network engineer, I should handle the network and also
postgresql d
Hi John,
I really don't know why I should keep the wal archives.
I implement streaming replication into 1 server (standby server).
I'm really newbie to PostgreSQL but the boss pushed me to handle it
and implement it in production f*&%*$%%$#%$#&# (forgive me)
They don't hire a database expert, I do
On 12/8/2015 4:55 PM, FattahRozzaq wrote:
...I want to limit the total size use by WAL archive to around 200-400 GB...?
for what purpose are you keeping a wal archive ?
if its for PITR (point in time recovery), you need ALL WAL records since
the start of a base backup up to the point in time
On 12/09/2015 11:15 AM, Alan Hodgson wrote:
On Wednesday, December 09, 2015 07:55:09 AM FattahRozzaq wrote:
archive_mode = on
archive_command = 'cp -i %p /home/postgres/archive/master/%f'
The WAL archive folder is at /home/postgres/archive/master/, right?
This directory consumes around 750GB o
On Wednesday, December 09, 2015 07:55:09 AM FattahRozzaq wrote:
> archive_mode = on
> archive_command = 'cp -i %p /home/postgres/archive/master/%f'
>
>
> The WAL archive folder is at /home/postgres/archive/master/, right?
> This directory consumes around 750GB of Disk-1.
> Each segment in the /ho
Hi all,
Please help...
I have 1 master PostgreSQL and 1 standby PostgreSQL.
Both servers has the same OS Linux Debian Wheezy, the same hardware.
Both server hardware:
CPU: 24 cores
RAM: 128GB
Disk-1: 800GB SAS (for OS, logs, WAL archive directory)
Disk-2: 330GB SSD (for PostgreSQL data directory
12 matches
Mail list logo
