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

From: Dmitri Maziuk <dmaziuk(at)bmrb(dot)wisc(dot)edu>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: WARNING: could not flush dirty data: Function not implemented
Date: 2018-09-03 17:32:32
Message-ID: 20180903123232.b0a465a54d5544b4b74bfcd5@bmrb.wisc.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 03 Sep 2018 09:58:57 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Ravi Krishna <sravikrishna(at)aol(dot)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(at)bmrb(dot)wisc(dot)edu>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Cramer 2018-09-03 17:35:30 Re: very slow largeobject transfers through JDBC
Previous Message Mate Varga 2018-09-03 16:59:53 Re: very slow largeobject transfers through JDBC