On Sun, Sep 02, 2018 at 04:31:18PM -0700, Andres Freund wrote:
> Please note that nobody has verified that postgres works correctly via
> the emulation stuff MS is doing. There is a native version of postgres
> for windows however, and that is tested (and exercised by a lot of
> installations).
I
Tom Lane writes:
> Ravi Krishna 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 lea
Tom Lane writes:
> Andres Freund writes:
>> On 2018-09-02 19:29:49 -0400, Tom Lane wrote:
>>> If this is on Ubuntu, I don't understand why you're talking
>>> about Windows.
>
>> The OP said "Ubuntu 18.04 as Windows bash" - so I assume this is
>> postgres compiled as a linux binary is running o
On 09/03/2018 12:41 PM, Austin Drenski wrote:
Dmitri Maziuk mailto:dmaz...@bmrb.wisc.edu>>
wrote:
> Tom Lane mailto:t...@sss.pgh.pa.us>> wrote:
>> Ravi Krishna mailto:sravikris...@aol.com>> writes:
Whee ... so you get to cope with all the bugs/idiosyncrasies of three
operating system
Dmitri Maziuk wrote:
> Tom Lane wrote:
>> Ravi Krishna 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,
On Mon, 03 Sep 2018 09:58:57 -0400
Tom Lane wrote:
> Ravi Krishna 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.
>
>
Ravi Krishna 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
>
> 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 ..
Andres Freund writes:
> On 2018-09-02 19:29:49 -0400, Tom Lane wrote:
>> If this is on Ubuntu, I don't understand why you're talking
>> about Windows.
> The OP said "Ubuntu 18.04 as Windows bash" - so I assume this is
> postgres compiled as a linux binary is running on MS's new-ish linux
> emulat
>That means that the linux emulation by microsoft isn't good enough. You
>can work around it by setting checkpoint_flush_after=0 and
>wal_writer_flush_after=0.
bgwriter_flush_after = 0# measured in pages, 0 disables
backend_flush_after = 0# measured in pages, 0 di
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.
>
> 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.
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.
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
14 matches
Mail list logo
