Re: [ADMIN] Off topic - Japanese PostgreSQL community

2011-03-15 Thread Fujii Masao
On Sun, Mar 13, 2011 at 3:54 AM, Rosser Schwarz wrote: > On Sat, Mar 12, 2011 at 11:46 AM, Bruce Momjian wrote: >> Benjamin Krajmalnik wrote: >>> Has anyone heard from the Japanese members of the community? > >> Yes, I posted a list of Japan members who have reported their safety to >> the Postgr

[ADMIN] Question about upgrading multiple clusters in v9.0.2

2011-03-15 Thread pkeenan
Greetings! We are running multiple clusters for development and test purposes. I was experimenting, as a PostgreSQL newbie, with upgrading from v9.0.1 to v9.0.2. I noticed that the installation of v9.0.2 did upgrade the default (original) cluster as part of the process. When I start the secon

Re: [ADMIN] Backup hot-standby database.

2011-03-15 Thread Robert Treat
On Tue, Mar 15, 2011 at 5:50 PM, Stephen Rees wrote: > Using PostgreSQL 9.0.x > > I cannot use pg_dump to generate a backup of a database on a hot-standby > server, because it is, by definition, read-only. That really makes no sense :-) You can use pg_dump on a read-only slave, but I think the i

Re: [ADMIN] Backup hot-standby database.

2011-03-15 Thread Kevin Grittner
Stephen Rees wrote: > I cannot use pg_dump to generate a backup of a database on a hot- > standby server, because it is, by definition, read-only. That seems like a non sequitur -- I didn't think pg_dump wrote anything to the source database. Have you actually tried? If so, please show your

[ADMIN] Backup hot-standby database.

2011-03-15 Thread Stephen Rees
Using PostgreSQL 9.0.x I cannot use pg_dump to generate a backup of a database on a hot- standby server, because it is, by definition, read-only. However, it seems that I can use COPY TO within a serializable transaction to create a consistent set of data file(s). For example, BEGIN TRANSA

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Bruce Momjian
Maria L. Wilson wrote: > good grief! - thanks for seeing that. > > ok, next question. so I change these permissions (to the correct read > perms :) > then how does postgres "load" these timezone? I'm really hoping that > this doesn't require a re-install. Restarting the server will fix it

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Maria L. Wilson
good grief! - thanks for seeing that. ok, next question. so I change these permissions (to the correct read perms :) then how does postgres "load" these timezone? I'm really hoping that this doesn't require a re-install. thanks again!! Maria Wilson On 3/15/11 4:12 PM, Tom Lane wrote:

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Tom Lane
"Maria L. Wilson" writes: > I would have thought the same thing too - but, the file system looks > correct.(below...) > -rw--- 3 root staff 3519 Nov 1 09:08 Eastern Well ... correct other than lacking read permissions for anybody but root ... regards, tom lan

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Maria L. Wilson
I would have thought the same thing too - but, the file system looks correct.(below...) [postgres@catalogdata share]$ cd timezone /scratch/postgresql-8.4.5/share/timezone [postgres@catalogdata timezone]$ ls -al total 268 drwxr-xr-x 19 root staff 4096 Nov 1 09:08 ./ drwxr-xr-x 9 root staf

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Tom Lane
"Maria L. Wilson" writes: > yes they are all running the same postgres version. - 8.4.5 > just as a test this morning - on one of the problem machines, we > installed another postgres installation - same version - just pointed it > to different paths - copied over the conf files and brought the

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Maria L. Wilson
when you say updating postgres - do you mean the server software? How do you update the tz data? I'm just a little concerned why only 2 of our machines (they are all supposed to be the same) are having this problem. On 3/15/11 2:08 PM, Scott Marlowe wrote: On Tue, Mar 15, 2011 at 6:50 AM, Ma

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Maria L. Wilson
it also looks like the view pg_timezone_names is empty in the problem installation. What loads this view? psql (8.4.5) Type "help" for help. postgres=# select * from pg_timezone_names; name | abbrev | utc_offset | is_dst --+++ (0 rows) postgres=# On 3/15/11

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Maria L. Wilson
yes they are all running the same postgres version. - 8.4.5 just as a test this morning - on one of the problem machines, we installed another postgres installation - same version - just pointed it to different paths - copied over the conf files and brought the server up. This time it was th

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Scott Marlowe
On Tue, Mar 15, 2011 at 12:17 PM, Scott Marlowe wrote: > On Tue, Mar 15, 2011 at 12:12 PM, Maria L. Wilson > wrote: >> when you say updating postgres - do you mean the server software?  How do >> you update the tz data? > > Yes updating the pg software. The OS has tzdata as well, and you can > up

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Scott Marlowe
On Tue, Mar 15, 2011 at 12:12 PM, Maria L. Wilson wrote: > when you say updating postgres - do you mean the server software?  How do > you update the tz data? Yes updating the pg software. The OS has tzdata as well, and you can update that. But postgresql includes its own tzdata so I'm guessing

Re: [ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Scott Marlowe
On Tue, Mar 15, 2011 at 6:50 AM, Maria L. Wilson wrote: > Hi all - > > Ever since daylight savings time, I've noticed that the timestamp in the log > files on 2 of our many postgres servers (version 8.4.5) did not update. >  It's still 1 hour behind.  The settings are all default (see below) on al

Re: [ADMIN] PSQLException: ERROR: could not open relation with OID xxxx

2011-03-15 Thread Kevin Grittner
"Gnanakumar" wrote: >> If that doesn't do it I might try adding zero to numbers and >> concatenating empty strings to try to prevent late use of the >> OID. (Essentially as a form of optimization barrier.) > > I couldn't understand this approach clearly. Can you help explain > me with some exa

[ADMIN] log timestamp since daylight saving time

2011-03-15 Thread Maria L. Wilson
Hi all - Ever since daylight savings time, I've noticed that the timestamp in the log files on 2 of our many postgres servers (version 8.4.5) did not update. It's still 1 hour behind. The settings are all default (see below) on all the servers. # - Locale and Formatting - datestyle = 'iso

Re: [ADMIN] PSQLException: ERROR: could not open relation with OID xxxx

2011-03-15 Thread Gnanakumar
> Clearly it's trying to use an OID it calculated for one of these > tables after the table has been dropped, and I suspect that the lock > is released between gathering the data and sorting it. I don't have > any 8.2 databases around to try this on, but perhaps you would avoid > it with a slight