пн, 2 дек. 2019 г. в 12:04, Laurenz Albe :
> On Sat, 2019-11-30 at 22:47 +0300, Eugene Podshivalov wrote:
> > It sounds strange but the "type" is indeed impacting the overall
> > performance somehow.
> > I've just tried to execute the following sequence of comm
onous_commit TO OFF;
SET client_encoding TO 'UTF8';
COPY ways FROM program 'cmd /c "type D:\ways.txt"';
ALTER TABLE ONLY ways ADD CONSTRAINT pk_ways PRIMARY KEY (id);
Regards
пт, 29 нояб. 2019 г. в 15:22, Eugene Podshivalov :
>
> Laurenz,
> There is no way
t constant but periodical, as if there are some
kind of dumps for recovery performed in the background.
maintenance_work_mem is the same in both cases.
Regards
пт, 29 нояб. 2019 г. в 15:04, Laurenz Albe :
>
> On Fri, 2019-11-29 at 13:04 +0300, Eugene Podshivalov wrote:
> > I'm usin
I don't think so. Why adding primary key shows the same downgraded
performance as well then?
пт, 29 нояб. 2019 г. в 13:37, Thomas Kellerer :
>
> Eugene Podshivalov schrieb am 29.11.2019 um 11:04:
> > Imported ways data from a file and added a primary key.
> >
> >
Hi,
I'm using PostgreSQL on Windows for Planet OSM database and have
noticed considirable decrease in performance when upgrading from v10
to 11 or 12. Here are the details of the experiment I conducted trying
to figure out what is causing the issue.
Installed PostgreSQL 10 from scratch. Created a
