Re: WARNING: could not flush dirty data: Function not implemented - Mailing list pgsql-general

From Dmitri Maziuk
Subject Re: WARNING: could not flush dirty data: Function not implemented
Date
Msg-id 20180903123232.b0a465a54d5544b4b74bfcd5@bmrb.wisc.edu
Whole thread Raw
In response to Re: WARNING: could not flush dirty data: Function not implemented  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WARNING: could not flush dirty data: Function not implemented  (Austin Drenski <austindrenski@gmail.com>)
List pgsql-general
On Mon, 03 Sep 2018 09:58:57 -0400
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Ravi Krishna <sravikrishna@aol.com> writes:
> >> Whee ... so you get to cope with all the bugs/idiosyncrasies of three
> >> operating system layers, not just one.  I concur that running Postgres
> >> in the underlying Windows O/S is probably a much better idea.
> 
> > Me too, but this is purely for learning and I am much more use to Linux stack then ... gasp Windows :-)
> 
> Hmm, so maybe you should install Ubuntu as the native O/S, and when
> you need Windows, run it inside a VM?
 
Between windows 10 and ubuntu 18.04, I would take a really close look at freebsd myself. Or at least alpine...

-- 
Dmitri Maziuk <dmaziuk@bmrb.wisc.edu>


pgsql-general by date:

Previous
From: Mate Varga
Date:
Subject: Re: very slow largeobject transfers through JDBC
Next
From: Dave Cramer
Date:
Subject: Re: very slow largeobject transfers through JDBC