[ADMIN] multiple standby configuration

2010-08-31 Thread Silvio Brandani
Is it possible to have multiple host destinations in the archive_command parameter of postgresql.conf to be able to mantain 2 standby datbase with write ahead log??? Can we use something like: archive_command = '/usr/bin/scp -Cv "%p" host_standby1:/var/lib/pgsql/archivelog/"%f" && /usr/bin/sc

Re: [ADMIN] multiple standby configuration

2010-08-31 Thread Jens Wilke
Am Dienstag 31 August 2010 11:36:31 schrieb Silvio Brandani: > Is it possible to have multiple host destinations in the archive_command > parameter of postgresql.conf to be able to mantain 2 standby datbase > with write ahead log??? You have to write a shell script and run this as archive command

[ADMIN] General migration question

2010-08-31 Thread Greg Spiegelberg
Probably questions best asked on hackers but I figure many are represented here. Will there ever be a release where a dump-restore is not necessary? Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not require a dump-restore? >From 9.0 Release Notes: E.1.2. Migration to Version 9.0 A dump

Re: [ADMIN] General migration question

2010-08-31 Thread Alvaro Herrera
Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010: > Probably questions best asked on hackers but I figure many are represented > here. > Will there ever be a release where a dump-restore is not necessary? > Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not requ

Re: [ADMIN] General migration question

2010-08-31 Thread Greg Spiegelberg
On Tue, Aug 31, 2010 at 9:07 AM, Alvaro Herrera wrote: > Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010: >> Probably questions best asked on hackers but I figure many are represented >> here. >> Will there ever be a release where a dump-restore is not necessary? >> Per

Re: [ADMIN] General migration question

2010-08-31 Thread Scott Marlowe
On Tue, Aug 31, 2010 at 9:33 AM, Greg Spiegelberg wrote: > On Tue, Aug 31, 2010 at 9:07 AM, Alvaro Herrera > wrote: >> Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010: >>> Probably questions best asked on hackers but I figure many are represented >>> here. >>> Will the

Re: [ADMIN] Tuple changes from relfilenodes

2010-08-31 Thread Bruce Momjian
Kevin Grittner wrote: > *ukasz Brodziak wrote: > > From: kevin.gritt...@wicourts.gov > > >> Are you looking for statistics or the actual prior versions of > >> rows? > > > I'm looking for actual versions of row data. What I want to > > achieve as a final result is a kind of data change history.

Re: [ADMIN] General migration question

2010-08-31 Thread Joshua D. Drake
On Tue, 2010-08-31 at 09:42 -0600, Scott Marlowe wrote: > > All I'm suggesting is lumping those things requiring a dump/restore > > together for major updates. > > That's exactly what does happen, if you remember that pgsql is > numbered major.major.minor. Perhaps thinking about it like this wil

[ADMIN] Confused by 'timing' results

2010-08-31 Thread A J
time echo '\timing \\select * from table1 where id = 123;' | psql I am trying to time a simple select statement from different clients located at different places. The database is on US east-coast. In the above query. the 'timing' will time the database time and the 'time' command at the very s

Re: [ADMIN] Confused by 'timing' results

2010-08-31 Thread Kevin Grittner
A J wrote: > time echo '\timing \\select * from table1 where id = 123;' | psql > In the above query. the 'timing' will time the database time and > the 'time' command at the very start will time the complete time > for the query including network time. No, the 'timing' will say how long it

Re: [ADMIN] Confused by 'timing' results

2010-08-31 Thread A J
OK, thanks Kevin. So to measure just the time take by database server, I guess I need to set the log_min_duration_statement and log_statement parameters in postgresql.conf log_min_duration_statement output should stay constant for all the different clients across different geographic locations.

Re: [ADMIN] Confused by 'timing' results

2010-08-31 Thread Kevin Grittner
A J wrote: > log_min_duration_statement output should stay constant for all the > different clients across different geographic locations. I'm not sure timings there will be totally immune to network speed. The whole execution engine is designed around the top level pulling rows from other le

[ADMIN] Changing locale to 1250

2010-08-31 Thread Łukasz Brodziak
Hello, The question is maybe stupid but it's a trouble to me. I would like to perform some tasks on my linux (ubuntu) using db from work unfortunatly the DB has WIN1250 encoding and the PostgreSQL in linux has UTF-8 is it possible to somehow change the server's locale as I may not change the e

Re: [ADMIN] Changing locale to 1250

2010-08-31 Thread Kevin Grittner
*ukasz Brodziak wrote: > I would like to perform some tasks on my linux (ubuntu) using db > from work unfortunatly the DB has WIN1250 encoding and the > PostgreSQL in linux has UTF-8 is it possible to somehow change the > server's locale as I may not change the encoding of the DB. Are you tryin

Re: [ADMIN] Changing locale to 1250

2010-08-31 Thread Łukasz Brodziak
The version in 8.4. I'm trying to copy the database from Windows to Linux. If it is of any importance the version of "Windows Postgres" is 8.2 > Date: Tue, 31 Aug 2010 14:37:19 -0500 > From: kevin.gritt...@wicourts.gov > To: lukasz.brodz...@hotmail.com; pgsql-admin@postgresql.org > Subject: Re:

Re: [ADMIN] Confused by 'timing' results

2010-08-31 Thread Scott Marlowe
On Tue, Aug 31, 2010 at 1:01 PM, A J wrote: > OK, thanks Kevin. So to measure just the time take by database server, I > guess I need to set the log_min_duration_statement and log_statement > parameters in postgresql.conf > log_min_duration_statement output should stay constant for all the differe

Re: [ADMIN] Changing locale to 1250

2010-08-31 Thread Kevin Grittner
*ukasz Brodziak wrote: > The version in 8.4. I'm trying to copy the database from Windows > to Linux. If it is of any importance the version of "Windows > Postgres" is 8.2 Use pg_dump from your 8.4 machine. I would use the --encoding switch when I ran pg_dump to get UTF-8 encoding in the dump