Re: WARNING: could not flush dirty data: Function not implemented

2018-09-02 Thread Andres Freund
Hi, On 2018-09-02 19:29:49 -0400, Tom Lane wrote: > Ravi Krishna writes: > > A simple search tells that this is an old problem and my Windows has > > necessary WSL and other subsystem for this error to not show up. > > If this is on Ubuntu, I don't understand why you're talking > about Windows.

Re: dat names generated by pg_dump

2018-09-02 Thread Ron
On 09/02/2018 09:26 PM, Tom Lane wrote: Ron writes: I can associate these dat names with their source tables through a bunch of bash and vim manual operations, but I was wondering if there's any automated method (maybe some SQL query of some catalog table; pg_class didn't seem to have the relev

Re: dat names generated by pg_dump

2018-09-02 Thread Tom Lane
Ron writes: > I can associate these dat names with their source tables through a bunch of > bash and vim manual operations, but I was wondering if there's any automated > method (maybe some SQL query of some catalog table; pg_class didn't seem to > have the relevant data) of making the associat

Re: dat names generated by pg_dump

2018-09-02 Thread Adrian Klaver
On 09/02/2018 07:07 PM, Ron wrote: On 09/02/2018 08:41 PM, Adrian Klaver wrote: On 09/02/2018 05:40 PM, Ron wrote: Hi, I can associate these dat names with their source tables through a bunch of bash and vim manual operations, but I was wondering if there's any automated method (maybe some S

Re: dat names generated by pg_dump

2018-09-02 Thread Ron
On 09/02/2018 08:41 PM, Adrian Klaver wrote: On 09/02/2018 05:40 PM, Ron wrote: Hi, I can associate these dat names with their source tables through a bunch of bash and vim manual operations, but I was wondering if there's any automated method (maybe some SQL query of some catalog table; pg_c

Re: WARNING: could not flush dirty data: Function not implemented

2018-09-02 Thread Ravi Krishna
> > If this is on Ubuntu, I don't understand why you're talking > about Windows. Because I am using Ubuntu Bash on Windows, which requires WLS (Windows Linux Subsystem). I also have necessary build version of Windows which supports Ubuntu Bash.

Re: dat names generated by pg_dump

2018-09-02 Thread Adrian Klaver
On 09/02/2018 05:40 PM, Ron wrote: Hi, I can associate these dat names with their source tables through a bunch of bash and vim manual operations, but I was wondering if there's any automated method (maybe some SQL query of some catalog table; pg_class didn't seem to have the relevant data) o

dat names generated by pg_dump

2018-09-02 Thread Ron
Hi, I can associate these dat names with their source tables through a bunch of bash and vim manual operations, but I was wondering if there's any automated method (maybe some SQL query of some catalog table; pg_class didn't seem to have the relevant data) of making the association. If relev

Re: WARNING: could not flush dirty data: Function not implemented

2018-09-02 Thread Andres Freund
Hi, On 2018-09-02 22:57:55 +, Ravi Krishna wrote: > Ubuntu 18.04 as Windows bash > > Distributor ID: Ubuntu > Description:Ubuntu 18.04.1 LTS > Release:18.04 > Codename: bionic > > > PG 10.5.1 > > postgres@ravi-lenovo:~$ psql -d postgres > psql (10.5 (Ubuntu 10.5-1.pgdg16.

Re: WARNING: could not flush dirty data: Function not implemented

2018-09-02 Thread Tom Lane
Ravi Krishna writes: > A CREATE DATABASE statement spewed out > WARNING: could not flush dirty data: Function not implemented Hmm, that's probably ENOSYS coming back from sync_file_range(). What filesystem is this database sitting on? It's harmless from a correctness standpoint, because we'll

WARNING: could not flush dirty data: Function not implemented

2018-09-02 Thread Ravi Krishna
Ubuntu 18.04 as Windows bash Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic PG 10.5.1 postgres@ravi-lenovo:~$ psql -d postgres psql (10.5 (Ubuntu 10.5-1.pgdg16.04+1)) A CREATE DATABASE statement spewed out WARNING: could not flush dirt

Re: pg_basebackup: could not receive data from WAL stream

2018-09-02 Thread Kaixi Luo
wal_sender_timeout should be as long as necessary. Each wal file is 16MB, so it should be *at least* as long as the time needed to transfer 16MB*wal_keep_segments. Take a look at the size of your pg_xlog folder. On Sun, Sep 2, 2018 at 3:41 PM Adrian Klaver wrote: > On 09/01/2018 09:06 PM, greigw

Re: locate DB corruption

2018-09-02 Thread Dave Peticolas
On Sun, Sep 2, 2018 at 4:51 AM Stephen Frost wrote: > Greetings, > > * Dave Peticolas (d...@krondo.com) wrote: > > On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver > > wrote: > > > > > On 09/01/2018 04:45 PM, Dave Peticolas wrote: > > > > > > > Well restoring from a backup of the primary does seem t

Re: pg_basebackup: could not receive data from WAL stream

2018-09-02 Thread Adrian Klaver
On 09/01/2018 09:06 PM, greigwise wrote: Hello. On postgresql 10.5, my pg_basebackup is failing with this error: pg_basebackup: could not receive data from WAL stream: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the r

Re: locate DB corruption

2018-09-02 Thread Stephen Frost
Greetings, * Dave Peticolas (d...@krondo.com) wrote: > On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver > wrote: > > > On 09/01/2018 04:45 PM, Dave Peticolas wrote: > > > > > Well restoring from a backup of the primary does seem to have fixed the > > > issue with the corrupt table. > > > > Pretty su