Re: [GENERAL] Hardware recommendations?

On Wed, Nov 2, 2016 at 4:19 PM, John R Pierce wrote: > On 11/2/2016 3:01 PM, Steve Crawford wrote: >> >> After much cogitation I eventually went RAID-less. Why? The only option >> for hardware RAID was SAS SSDs and given that they are not built on >> electro-mechanical

Re: [GENERAL] Replication (BDR) problem: won't catch up after connection timeout

See also https://github.com/2ndQuadrant/bdr/issues/233 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Replication (BDR) problem: won't catch up after connection timeout

Increase wal_sender_timeout to resolve the issue. I've been investigating just this issue recently. See https://www.postgresql.org/message-id/camsr+ye2dsfhvr7iev1gspzihitwx-pmkd9qalegctya+sd...@mail.gmail.com . It would be very useful to me to know more about the transaction that caused this

[GENERAL] libpq backwards compatbility

We have a libpq application written in C++. There are existing running deployments of our application that were compiled against PostgreSQL version 9.3. We want to move to PostgreSQL version 9.6. Can we assume that the 9.6 libpq library is backwards compatible with applications compiled

Re: [GENERAL] Recover from corrupted database due to failing disk

On 11/2/16 6:21 PM, Jim Nasby wrote: I wouldn't trust the existing cluster that far. Since it sounds like you have no better options, you could use zero_damaged_pages to allow a pg_dumpall to complete, but you're going to end up with missing data. So what I'd suggest would be: stop Postgres

Re: [GENERAL] Recover from corrupted database due to failing disk

On 11/2/16 2:02 PM, Gionatan Danti wrote: However, backup continue to fail with "invalid page header in block" message. Morever, I am very near the xid wraparound limit and, as vacuum fails due to the invalid blocks, I expect a database shutdown (triggered by the 1M transaction protection)

Re: [GENERAL] Questions on Post Setup MASTER and STANDBY replication - Postgres9.1

On 11/2/16 2:49 PM, Joanna Xu wrote: The replication is verified and works. My questions are what’s the reason causing “cp: cannot stat `/opt/postgres/9.1/archive/00010003': No such file or directory” on STANDBY and how to fix it? What instructions/tools did you use to setup

Re: [GENERAL] initdb createuser commands

On 10/31/16 9:50 AM, Christofer C. Bell wrote: He's getting a lot of pushback that really feels it's coming from the wrong direction. "Just learn it." "It's always been this way." "No one agrees with you." These arguments are unconvincing. That said, there's nothing wrong with just saying,

Re: [GENERAL] Checking Postgres Streaming replication delay

On 10/31/16 3:39 PM, Patrick B wrote: |( ||extract(epoch FROMnow())- ||extract(epoch FROMpg_last_xact_replay_timestamp()) ||)::int lag| You could certainly simplify it though... extract(epoch FROM now()-pg_last_xact_replay_timestamp()) -- Jim Nasby, Data Architect, Blue Treble Consulting,

Re: [GENERAL] Hardware recommendations?

On 11/2/2016 3:01 PM, Steve Crawford wrote: After much cogitation I eventually went RAID-less. Why? The only option for hardware RAID was SAS SSDs and given that they are not built on electro-mechanical spinning-rust technology it seemed like the RAID card was just another point of solid-state

Re: [GENERAL] Hardware recommendations?

After much cogitation I eventually went RAID-less. Why? The only option for hardware RAID was SAS SSDs and given that they are not built on electro-mechanical spinning-rust technology it seemed like the RAID card was just another point of solid-state failure. I combined that with the fact that the

[GENERAL] Google Cloud Compute

Hello, I’m considering moving my servers to Google. The main reason is the transparent encryption they offer. This means I should either move all or none. The former would include PostreSQL, specifially: FreeBSD + ZFS + PostgreSQL. Do you have any pros or cons based on experience? (Would

Re: [GENERAL] Hardware recommendations?

On Wed, Nov 2, 2016 at 11:40 AM, Joshua D. Drake wrote: > On 11/02/2016 10:03 AM, Steve Atkins wrote: >> >> I'm looking for generic advice on hardware to use for "mid-sized" >> postgresql servers, $5k or a bit more. >> >> There are several good documents from the 9.0 era,

[GENERAL] Questions on Post Setup MASTER and STANDBY replication - Postgres9.1

Hi All, After setting up two nodes with MASTER and STANDBY replication, I see " cp: cannot stat `/opt/postgres/9.1/archive/00010003': No such file or directory" in the log on STANDBY and the startup process recovering "00010004" which does not exist in the

Re: [GENERAL] Hardware recommendations?

On 11/02/2016 10:03 AM, Steve Atkins wrote: I'm looking for generic advice on hardware to use for "mid-sized" postgresql servers, $5k or a bit more. There are several good documents from the 9.0 era, but hardware has moved on since then, particularly with changes in SSD pricing. Has anyone

[GENERAL] Hardware recommendations?

I'm looking for generic advice on hardware to use for "mid-sized" postgresql servers, $5k or a bit more. There are several good documents from the 9.0 era, but hardware has moved on since then, particularly with changes in SSD pricing. Has anyone seen a more recent discussion of what someone

[GENERAL] Replication (BDR) problem: won't catch up after connection timeout

Hi there, We have some problems with BDR and would appreciate any hints and advice with it. Here's the short story: We are testing BDR with PostgreSQL 9.4 and it seems to work quite ok after getting it up and running, but we ran into a quite disturbing weakness also. A basic two node cluster