Re: Unlogged tables cleanup - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Unlogged tables cleanup
Date
Msg-id CAB7nPqRCk-bXEDkm4QXSLKzWh5X8rBw0Jb9iTKi11tUrPX64JQ@mail.gmail.com
Whole thread Raw
In response to Re: Unlogged tables cleanup  (konstantin knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Unlogged tables cleanup
List pgsql-hackers
On Thu, Nov 10, 2016 at 4:23 PM, konstantin knizhnik
<k.knizhnik@postgrespro.ru> wrote:
> No, it is latest sources from Postgres repository.
> Please notice that you should create new database and tablespace to reproduce this issue.
> So actually the whole sequence is
>
> mkdir fs
> initdb -D pgsql
> pg_ctl -D pgsql -l logfile start
> psql postgres
> # create tablespace fs location '/home/knizhnik/dtm-data/fs';
> # set default_tablespace=fs;
> # create unlogged table foo(x integer);
> # insert into foo values(generate_series(1,100000));
> # ^D
> pkill -9 postgres
> pg_ctl -D pgsql -l logfile start
> # select * from foo;

OK, I understood what I was missing. This can be reproduced with
wal_level = minimal. When using hot_standby things are working
properly.
-- 
Michael



pgsql-hackers by date:

Previous
From: konstantin knizhnik
Date:
Subject: Re: Unlogged tables cleanup
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: Patch: Implement failover on libpq connect level.