Hello Yora Sokolov,
On 18.03.2011 09:22, Yura Sokolov wrote:
postgres=# set timezone='+03:00';
SET
postgres=# select now();
now
--
2011-03-18 05:20:35.46008-03
(1 row)
Maybe this is not a bug - just an inconsistence:
Look here (tested with 9.0):
=#
On 15.03.2011 15:23, mac wrote:
when i install the software, after i choose the directory of software, the
SETUP need me input the password. this afternoon in another computer, i
input "postgres" to continue, but at my home, i try "postgres" or
"postgrespass", it all says "the password specified
>
> input "postgres" to continue, but at my home, i try "postgres" or
> "postgrespass", it all says "the password specified was incorrect. Please
> enter the correct password for the postgres windows user account", so i
> cant
> continue.
> please help me!
>
> On this computer there is allready a p
The following bug has been logged online:
Bug reference: 5937
Logged by: Etienne Robillard
Email address: e...@gthcfoundation.org
PostgreSQL version: 8.4.7
Operating system: GNU/Linux 2.6.38 (Debian)
Description:initdb: FATAL error: could not open relation with OID
26
I understand now that I must use America/New_York for DST to function. I
see in select * from pg_timezone_names ; that 'EDT' is a shortcut. I tried
to SET TIME ZONE 'EDT'; but PG doesn't seem to like that.
My problem is that the corrected time zone (America/New_York) doesn't seem
to stick after u
To make this even weirder, this effect only seems to happen to the
'postgres' user. When I use the 'bucardo' user, the time zone is correct!
postgres@Cloud-DB1:~$ psql beta_cms_main -c "select now();"
now
---
2011-03-21 08:22:37.521213-05
(1 row)
postgre
"Etienne Robillard" writes:
> Could not run initdb --no-locale -D $PGDATA as pgsql
> user to setup the internal postgresql db:
> Script started on Mon 21 Mar 2011 07:44:29 AM EDT
> $ /usr/local/pgsql/bin/initdb --no-locale -D $PGDATA
> The files belonging to this database system will be owned by
On Mon, Mar 21, 2011 at 9:13 AM, Jonathan Brinkman
wrote:
> I understand now that I must use America/New_York for DST to function. I
> see in select * from pg_timezone_names ; that 'EDT' is a shortcut. I tried
> to SET TIME ZONE 'EDT'; but PG doesn't seem to like that.
>
> My problem is that the
PostgreSQL is 8.4.7, WAL-Logshipping is actually using SkyTools 2.1.12
(both installed from PGDG rpms), running with CentOS 5.5 XEN-VM with Kernel
2.6.18-194.26.1.el5xen.
recovery.conf on the standby installed by walmgr is
restore_command = '/usr/bin/walmgr.py
/media/pgarchive/wal-config/wal-
On 21/03/11 11:00 AM, Tom Lane wrote:
> "Etienne Robillard" writes:
>
>> Could not run initdb --no-locale -D $PGDATA as pgsql
>> user to setup the internal postgresql db:
>>
>
>> Script started on Mon 21 Mar 2011 07:44:29 AM EDT
>> $ /usr/local/pgsql/bin/initdb --no-locale -D $PGDATA
>
10 matches
Mail list logo