Re: [GENERAL] High Level Committers Wanted

Understood and I agree. I will check to see how much contact detail I can divulge in an open forum. -- View this message in context: http://postgresql.1045698.n5.nabble.com/High-Level-Committers-Wanted-tp5795695p5795729.html Sent from the PostgreSQL - general mailing list archive at Nabble.com

Re: [GENERAL] High Level Committers Wanted

Your professional input is greatly appreciated. -- View this message in context: http://postgresql.1045698.n5.nabble.com/High-Level-Committers-Wanted-tp5795695p5795720.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-ge

Re: [GENERAL] High Level Committers Wanted

Two valid questions. 1. Columbia, Maryland 2. US Government Attending PGCon does make sense, however I was asked specifically to see if I could get someone for an onsite meeting. -- View this message in context: http://postgresql.1045698.n5.nabble.com/High-Level-Committers-Wanted-tp5795695p579

[GENERAL] High Level Committers Wanted

I am currently working for the Government and there is a huge push to move our Oracle databases to a FOSS database solution. Right now, PostgreSQL is high on the list. What we need is a meeting/training session with the main contributors to Postgres to help facilitate solutions of some of the Orac

Re: [GENERAL] Streaming Replication - Error on Standby

Thanks for the information and the URLs! -- View this message in context: http://postgresql.1045698.n5.nabble.com/Streaming-Replication-Error-on-Standby-tp5791463p5791588.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql

Re: [GENERAL] Streaming Replication - Error on Standby

To get the standby server to a point, I tool a globals dump and a data dump of the primary server and build the standby. Then I executed pg_startbackup, rsync data dir to standby data dir (to catch any changes made while I was building the standby) and finally pg_stopbackup... all on the primary

[GENERAL] Streaming Replication - Error on Standby

Postgres 9.3.2. RHEL 5 After performing all of the Streaming Replication setup steps, I get the following error message in my standby DB log file. database system identifier differ between the primary and standby I've double checked the recovery.conf file and it contains the correct hostname,

[GENERAL] Analyze during a transaction

I am running Postgres 9.3 on RedHat Linux 5.6. During the transaction data is deleted from our database, then an analyze is performed. If I analyze our database during a transaction and the transaction fails (rollback occurs), with the table statistics rollback to their original values? -- Vie