After installing my new server I just discovered something that doesn't seem
right:
sudo du -h /var/lib/postgresql/9.2/main
4.0K/var/lib/postgresql/9.2/main/pg_snapshots
4.0K/var/lib/postgresql/9.2/main/pg_serial
4.0K/var/lib/postgresql/9.2/main/pg_tblspc
29M
On Mon, Mar 18, 2013 at 10:14 AM, Niels Kristian Schjødt
nielskrist...@autouncle.com wrote:
After installing my new server I just discovered something that doesn't seem
right:
sudo du -h /var/lib/postgresql/9.2/main
snip
As you can see the pg_xlog folder is 202G, which is more than my
Okay, thanks. It' seems you were right! Now I have fixed the issue (it was an
ssh key).
So I started a:
SELECT pg_start_backup('backup', true);
And when done, I executed a:
sudo -u postgres rsync -av --exclude postmaster.pid --exclude pg_xlog
/var/lib/postgresql/9.2/main/
Thanks! it worked! :-)
Den 18/03/2013 kl. 15.38 skrev Magnus Hagander mag...@hagander.net:
On Mon, Mar 18, 2013 at 2:08 PM, Niels Kristian Schjødt
nielskrist...@autouncle.com wrote:
Okay, thanks. It' seems you were right! Now I have fixed the issue (it was
an ssh key).
So I started a:
Hi guys, I am worried about the effective_cache_size.
I run a 32-bits postgres installation on a machine with 64 bits kernel.
Should I limit effective_cache_size to a maximum of 2.5gb?
On Mon, Mar 18, 2013 at 10:53 AM, Rodrigo Barboza
rodrigombu...@gmail.com wrote:
Hi guys, I am worried about the effective_cache_size.
I run a 32-bits postgres installation on a machine with 64 bits kernel.
Should I limit effective_cache_size to a maximum of 2.5gb?
That variables refers to fs
Hello
2013/3/18 Rodrigo Barboza rodrigombu...@gmail.com:
Hi guys, I am worried about the effective_cache_size.
I run a 32-bits postgres installation on a machine with 64 bits kernel.
Should I limit effective_cache_size to a maximum of 2.5gb?
sure and probably little bit less
Regards
Pavel
Ok, now I'm lost, who is right about the limit? Rob or Pavel?
Rob, I know it should be a 64 bit, and it will be soon, but there are good
reasons for this scenario and it's ok for now.
On Mon, Mar 18, 2013 at 3:15 PM, Pavel Stehule pavel.steh...@gmail.comwrote:
Hello
2013/3/18 Rodrigo
2013/3/18 Pavel Stehule pavel.steh...@gmail.com:
Hello
2013/3/18 Rodrigo Barboza rodrigombu...@gmail.com:
Hi guys, I am worried about the effective_cache_size.
I run a 32-bits postgres installation on a machine with 64 bits kernel.
Should I limit effective_cache_size to a maximum of 2.5gb?
So setting this as half of ram, as suggested in postgres tuning webpage
should be safe?
It says it is a conservative value...
On Mon, Mar 18, 2013 at 3:18 PM, Pavel Stehule pavel.steh...@gmail.comwrote:
2013/3/18 Pavel Stehule pavel.steh...@gmail.com:
Hello
2013/3/18 Rodrigo Barboza
Rodrigo Barboza rodrigombu...@gmail.com wrote:
So setting this as half of ram, as suggested in postgres tuning
webpage should be safe?
Half of RAM is likely to be a very bad setting for any work load.
It will tend to result in the highest possible number of pages
duplicated in PostgreSQL and
On Mon, Mar 18, 2013 at 3:47 PM, Kevin Grittner kgri...@ymail.com wrote:
Rodrigo Barboza rodrigombu...@gmail.com wrote:
So setting this as half of ram, as suggested in postgres tuning
webpage should be safe?
Half of RAM is likely to be a very bad setting for any work load.
It will tend to
2013/3/18 Kevin Grittner kgri...@ymail.com:
Rodrigo Barboza rodrigombu...@gmail.com wrote:
So setting this as half of ram, as suggested in postgres tuning
webpage should be safe?
Half of RAM is likely to be a very bad setting for any work load.
It will tend to result in the highest possible
13 matches
Mail list logo
