Re: [GENERAL] replication timeout in pg_basebackup

Thats exactly what I was thinking after all other experiments. Couple of questions: 1) why did you say that 300 seconds is the upper limit? Is this enforced by Postgres? What if I want to set it to 10 minutes? 2) whats the downside of bigger replication timeout? Thanks. Ajay

Re: [GENERAL] replication timeout in pg_basebackup

Non-Sync'ed 8kB writes: write 202216.900 ops/sec From: Haribabu Kommi [kommi.harib...@gmail.com] Sent: Monday, March 10, 2014 1:42 AM To: Aggarwal, Ajay Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] replication timeout

Re: [GENERAL] replication timeout in pg_basebackup

or force it to use direct I/O. From: Haribabu Kommi [kommi.harib...@gmail.com] Sent: Monday, March 10, 2014 8:31 PM To: Aggarwal, Ajay Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] replication timeout in pg_basebackup On Tue, Mar 11, 2014 at 7:07 AM

[GENERAL] replication timeout in pg_basebackup

Our environment: Postgres version 9.2.2 running on CentOS 6.4 Our backups using pg_basebackup are frequently failing with following error pg_basebackup: could not send feedback packet: server closed the connection unexpectedly This probably means the server terminated abnormally

[GENERAL] Segmentation fault

hello team , i am trying to enter this insert command in postgres insert into mmsuper.notification values('101','12','13','حب|welcome|आपकास्वागतहै','bye','goodbye','low balance',5); now when i am trying to paste this in postgres in Solaris , it is giving me error fm_db_Server1-# insert into

Re: [GENERAL] Segmentation fault

thanks for the reply ,.. When i am trying to enter anything else other then some Arabic , Hindi .. that case it does not give this error. like if i enter.. insert into table values('welcome',1); then it does not give any error and get successfully Thanks -- View this message in context:

Re: [GENERAL]

Everybody wants to be happy! You will be happy with it!... http://masdeltechno.com/com.page.php?ihotmailID=12ek8 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Amazon EC2 | Any recent developments

Hello All, I am investigating the possibility of hosting pgsql 8.3 on Amazon EC2 implementing a simple HA solution. My search of postgresql amazon cloud has produced little result. Just wondering if there has been any recent development with EBS etc. and anybody would care to share their

[GENERAL] Help Needed in Postgis

Hi, I'm new to the mapserver and postgis system. I'm not very familiar with the structure applications involving these. My query is probably a very elementry one . Can someone please help me resolve this.AIM: I have a working Mapserver demo application, the common one which displays the map of

[GENERAL] Getting error regarding pg_config_os.h file not there

Can anybody is having any solution about this. I just want to know that wehter these files are generated when we install PostgreSql. Because these files are not present on my system -Ajay Dalvi ---(end of broadcast)--- TIP 1: subscribe

[GENERAL] How to uninstall PostGreSql from linux

Hello all, I am having POstGreSql version 7.2 Please tell me the procedure to uninstall PostGreSql -Ajay ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

[GENERAL] Error while installing Slony 1.1.0 for PostGreSql version 7.3.4

of PostgreSQL... 7.3 checking for PQunescapeBytea in -lpq... no configure: error: Your version of libpq doesn't have PQunescapeBytea this means that your version of PostgreSQL is lower than 7.3 and thus not supported by Slony-I. Regards, -Ajay Dalvi ---(end

[GENERAL] Error while installing Slony 1.1.0 for PostGreSql version 7.3.4

of PostgreSQL... 7.3 checking for PQunescapeBytea in -lpq... no configure: error: Your version of libpq doesn't have PQunescapeBytea this means that your version of PostgreSQL is lower than 7.3 and thus not supported by Slony-I. Regards, -Ajay Dalvi ---(end

[GENERAL] what if PQexec() result is toooooo big?

me the next 500", and so on... until you read the entire table. How does postgres handle these situations? Ajay