Re: BUG #14378: when drop schema, standby will do many more than primary, and very slow, it's a bug? - Mailing list pgsql-bugs

From 德哥
Subject Re: BUG #14378: when drop schema, standby will do many more than primary, and very slow, it's a bug?
Date
Msg-id 1b0753d6.1bcc.157da888833.Coremail.digoal@126.com
Whole thread Raw
In response to Re: BUG #14378: when drop schema, standby will do many more than primary, and very slow, it's a bug?  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs

HI,
   Thanks Andres Freund's replay.
Btw, schema not like database in file struct, it has no directory entry below the database directory.
database has a dir below tablespace dir. but schema no dir below the database dir .
so drop schema must deal files one-by-one?
but drop database can drop dir only?

best regards.



--
公益是一辈子的事,I'm Digoal,Just Do It.


At 2016-10-19 02:32:08, "Andres Freund" <andres@anarazel.de> wrote: >On 2016-10-18 07:57:33 +0000, digoal@126.com wrote: >> The following bug has been logged on the website: >> >> Bug reference: 14378 >> Logged by: Zhou Digoal >> Email address: digoal@126.com >> PostgreSQL version: 9.6.0 >> Operating system: CentOS 6.x x64 >> Description: >> >> >> >> when i use postgresql 9.6.0 for primary-standby, i drop a schema on primary, >> but it's apply very slow on standby. >> >> the wal send very fast, but apply very slow, i think the syscall more than >> it on primary? >> >> this is my test: > >There's some O(n^2) behaviour around lock release and acquire during >replay IIRC. See for example the thread around >http://archives.postgresql.org/message-id/20140630231741.GA30918%40alap3.anarazel.de > >It's not entirely trivial to fix that though. E.g. the patch of Simon's >later in that thread wouldn't help in your situation. > >Greetings, > >Andres Freund

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Return Codes of BatchUpdateException in PostgreSql 9.6
Next
From: 德哥
Date:
Subject: Re: BUG #14378: when drop schema, standby will do many more than primary, and very slow, it's a bug?