Re: [ADMIN] [GENERAL] Using of replication by initdb for both nodes?

2013-08-30 Thread Michael Paquier
On Thu, Aug 29, 2013 at 11:06 PM, Bocap wrote: > 1. Instead of using pg_basebackup for standby DB, i initdb for both standby > and primary. > 2. Create recovery.conf in standby DB, and start both nodes. > Now it work fine for me, but is it sure that no problem? A standby node *needs* to be based o

[ADMIN] to_timestamp error between postgres version 8.3 and 9.2

2013-08-30 Thread Technical Doubts
Dear Team, I have a table with name registers_info with below columns regid character varying, transid bigint, regdate timestamp without time zone, canceldate timestamp without time zone insert into registers_info (regid,transid,regdate,canceldate) values ('reg1',1,to_timestamp('2013-07-24','yy

Re: [ADMIN] to_timestamp error between postgres version 8.3 and 9.2

2013-08-30 Thread Tom Lane
Technical Doubts writes: > insert into registers_info (regid,transid,regdate,canceldate) values > ('reg1',1,to_timestamp('2013-07-24','-MM-dd > hh24:mi:ss')::TIMESTAMP,to_timestamp('null','-MM-dd > hh24:mi:ss')::TIMESTAMP); > The above query works fine in Postgres 8.3 version. > But the

Re: [ADMIN] to_timestamp error between postgres version 8.3 and 9.2

2013-08-30 Thread françois Figarola
I think it's only a syntax problem : to_timestamp('null','-MM-ddhh24:mi:ss')::TIMESTAMP In this form your 'null' parameter is a text which dont match for your definition, so the function is waiting for an integer representing the year and fails. But if you write : to_timestamp(null,'-MM