Il 03-11-2016 00:21 Jim Nasby ha scritto:
On 11/2/16 2:02 PM, Gionatan Danti wrote:
That means at least some of the Postgres files have been damaged
(possibly due to the failing disk). Postgres will complain when it
sees internal data structures that don't make sense, but it has no way
to know i
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 spinning-rust technology it
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
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 prob
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 agai
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
make
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) within
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
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, "
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, Aust
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
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
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 fsy
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, but hardware has moved
>>
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 archiv
Dear all,
some days ago I was tasked to recover a production database from a
failing single-disk (!) system. I initially planned to restore from
backups but, due to the bad disk, backups (done via pg_dumpall) were
failing and nobody cared to notice (!!). Bottom line, the system was
failing and
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 se
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 mi
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 b
19 matches
Mail list logo
