[GENERAL] Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\

2016-07-18 Thread sudalai
@micheal, Thanks for your help. It working now. But, now I'm getting deadlock, when i peek_changes or get_changes, in live system. db=#select count(*) from pg_logical_slot_peek_changes('slot',NULL,100); /* pid : 25833 */ ERROR: deadlock detected DETAIL: Process 25833 waits for Sha

Re: [GENERAL] Strange array_to_table / unnest result

2016-07-18 Thread Johann Spies
> Unnest is evaluated before LIMIT > You need to use derived table > > postgres=# select unnest(a) from (select a from x limit 1) si > Thank you! Regards Johann

Re: [GENERAL] Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\

2016-07-18 Thread Michael Paquier
On Mon, Jul 18, 2016 at 4:31 PM, sudalai wrote: > Please help me, I am using PostgreSQL 9.5.0. > I don't know much in postgres internals. why does peek_changes trying > to take share lock on 248486 (primary key of one table). > Its postgres logical decoder takes share lock or outpu

[GENERAL] Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\

2016-07-18 Thread sudalai
thank u. why (select * from pg_logical_slot_peek_changes('slot',NULL,1) ) take share lock ? any idea ? -Sudalai - sudalai -- View this message in context: http://postgresql.nabble.com/ERROR-missing-chunk-number-0-for-toast-value-while-using-logical-decoder-tp5909194p5912411.html Se

Re: [GENERAL] Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\

2016-07-18 Thread Michael Paquier
On Mon, Jul 18, 2016 at 7:08 PM, sudalai wrote: > thank u. > why (select * from pg_logical_slot_peek_changes('slot',NULL,1) ) take share > lock ? > any idea ? My guess is that this lock comes from your plugin code. Please double-check it. -- Michael -- Sent via pgsql-general mailing list (p

[GENERAL] Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\

2016-07-18 Thread sudalai
Got it. Thank you very much. :) -Sudalai - sudalai -- View this message in context: http://postgresql.nabble.com/ERROR-missing-chunk-number-0-for-toast-value-while-using-logical-decoder-tp5909194p5912426.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent

[GENERAL] Congratulations (EDB) on U.S. Security Technical Implementation Guide.

2016-07-18 Thread John McKown
May be of interest to some here. EDB is the commercial enhancement to PostgreSQL. http://www.enterprisedb.com/news-events/press-releases/us-government-publishes-edb-postgres-advanced-server-security-technical-i Release Date: Jul 14, 2016 *EDB Postgres Advanced Server STIG becomes first open sour

Re: [GENERAL] MongoDB 3.2 beating Postgres 9.5.1?

2016-07-18 Thread Kisung Kim
Hi, I recently test YCSB benchmark too. But contrary to my expectation, PG (9.5) is slower than MongoDB 3.2. Paul said that making table with no logging option improved the performance, and it might be equal to MongoDB's behavior. But in MongoDB documentation, it writes journal log too. So I think

Re: [GENERAL] MongoDB 3.2 beating Postgres 9.5.1?

2016-07-18 Thread Sameer Kumar
On Fri, 11 Mar 2016, 9:39 p.m. Paul Jones, wrote: > I have been running the EDB benchmark that compares Postgres and MongoDB. > I believe EDB ran it against PG 9.4 and Mongo 2.6. I am running it > against PG 9.5.1 and Mongo 3.2 with WiredTiger storage using 10,000,000 > JSON records generated by

Re: [GENERAL] MongoDB 3.2 beating Postgres 9.5.1?

2016-07-18 Thread Kisung Kim
Of course, I do not create GIN index. Maybe the problem is related to checkpoint and WAL. I don't know how to make the comparison with MongoDB fair enough. (C)Bitnine, Kisung Kim, Ph.D https://sites.google.com/site/kisungresearch/ E-mail : ks...@bitnine.net Office phone : 070-4800-5890, 408-60

[GENERAL] MediaWiki + PostgreSQL is not ready for production?

2016-07-18 Thread Tatsuo Ishii
I found following comment for using PostgreSQL with MediaWiki: https://www.mediawiki.org/wiki/Compatibility#Database "Anything other than MySQL or MariaDB is not recommended for production use at this point." This is a sad and disappointed statement for us. Should we help MediaWiki community to

Re: [GENERAL] MediaWiki + PostgreSQL is not ready for production?

2016-07-18 Thread John R Pierce
On 7/18/2016 9:14 PM, Tatsuo Ishii wrote: I found following comment for using PostgreSQL with MediaWiki: https://www.mediawiki.org/wiki/Compatibility#Database "Anything other than MySQL or MariaDB is not recommended for production use at this point." This is a sad and disappointed statement fo