ended settings. Is there a way to get those information on the
server itself from psql?
regards,
Alexander Al
On 20/2/20 15:47, Tom Lane wrote:
>
> Unfortunately, not having an up-to-date copy of the xlog info is
> practically fatal to your hopes of getting back consistent data.
> [...]
>
Ok, so if the only way to restore the data is getting the content in
pg_xlog directory I'm looking for it.
I went to
Hello. I'm trying to restore/rescue a database from some that I have:
* I have all the recent files in PGDATA/base
(/var/lib/postgresql/9.6/main/base/), but I have not the complete
/var/lib/postgresql/9.6/main/
* I have all files from an old backup (and not much different) dump
that I rest
> The only *error* I see is when you apparently manually kill the process.
You mean walreceiver process?? 'FATAL: terminating walreceiver process due
to administrator command' ?
Actually, I didn't kill the receiver. It is done by postgres itself, as far
as I understand.
I restart this node using
ts
On Wed, Jan 30, 2019 at 7:44 AM Michael Paquier wrote:
> On Tue, Jan 29, 2019 at 07:13:11PM +0600, Abdullah Al Maruf wrote:
> > When I try to attach an old master with 'archiving set to on` as a new
> > standby, `pg_rewind` doesn't throw any error, But, when the datab
When I try to attach an old master with 'archiving set to on` as a new
standby, `pg_rewind` doesn't throw any error, But, when the database
starts, The following error appears:
```
LOG: invalid record length at 0/B98: wanted 24, got 0
LOG: started streaming WAL from primary at 0/B00 on t
Hello,
I am trying to build an automated system in docker/kubernetes where a
container/pod will automatically schedule itself as a Master or Standby.
In short, I have 1 master nodes (0th node) and three standby nodes (1st,
2nd & 3rd node). When I make the 3rd node as master (by trigger file) and
r
