Hi,
maybe filesystem-snapshots with wal's are your solution. There
is a block-device replication-tool too. It's called drbd
(http://www.drbd.org). I never tested/used it, but i heard it
should be fine.
I'm using rsync/xfs_freeze to make incremental filesystem-snapshots
(incremental by hardlinks)
Hi,
I have a couple of issues.
One is regarding a file called 'fsync' and the other is related to
the sharedBuffers issue.
1) I am new to administering postgresql. When I was wandering
through the configuration files for the PostgreSQL, I observed the
'fsync' file. This file is almost id
Kishore B <[EMAIL PROTECTED]> writes:
> 1) I am new to administering postgresql. When I was wandering
> through the configuration files for the PostgreSQL, I observed the
> 'fsync' file. This file is almost identical to the postgresql.conf
> file, but with differing values for parameters and som
Hello All,
I need a reliable way to determine the overall size of our database.
Recently, I started using the database_size() function from the dbsize
contrib.
Everything seems to work great until I need to delete records.
After I DELETE records, the pg_autovacuum daemon kicks in an runs a VACUUM