Re: [PERFORM] Guidelines on best indexing strategy for varying searches on 20+ columns

2014-07-01 Thread Niels Kristian Schjødt
Thanks for the answers. > Den 30/06/2014 kl. 20.04 skrev Jeff Janes : > > On Wed, Jun 25, 2014 at 1:48 AM, Niels Kristian Schjødt > wrote: >> Hi, >> I’m running a search engine for cars. It’s backed by a postgresql 9.3 >> installation. >> >> Now I’m unsure about the best approach/strategy on d

Re: [PERFORM] Postgres Replaying WAL slowly

2014-07-01 Thread Tom Lane
Jeff Frost writes: >> On Jun 30, 2014, at 4:04 PM, Tom Lane wrote: >>> Did you check whether the locks were all on temp tables of the >>> ON COMMIT DROP persuasion? > And indeed it did catch up overnight and the lag increased shortly after a > correlating spike in AccessExclusiveLocks that were

Re: [PERFORM] Postgres Replaying WAL slowly

2014-07-01 Thread Jeff Frost
On Jun 30, 2014, at 4:57 PM, Jeff Frost wrote: > > On Jun 30, 2014, at 4:04 PM, Tom Lane wrote: > >> Ah ... that's more like a number I can believe something would have >> trouble coping with. Did you see a noticeable slowdown with this? >> Now that we've seen that number, of course it's poss

Re: [PERFORM] Volatility - docs vs behaviour?

2014-07-01 Thread Merlin Moncure
On Mon, Jun 30, 2014 at 9:15 PM, Tom Lane wrote: > Craig Ringer writes: >> I was unaware that the planner made any attempt to catch users' errors >> in marking the strictness of functions. I thought it pretty much trusted >> the user not to lie about the mutability of functions invoked >> indirec

Re: [PERFORM] 60 core performance with 9.3

2014-07-01 Thread Andres Freund
On 2014-07-01 21:48:35 +1200, Mark Kirkwood wrote: > On 27/06/14 21:19, Andres Freund wrote: > >On 2014-06-27 14:28:20 +1200, Mark Kirkwood wrote: > >>My feeling is spinlock or similar, 'perf top' shows > >> > >>kernel find_busiest_group > >>kernel _raw_spin_lock > >> > >>as the top time users. > >

Re: [PERFORM] 60 core performance with 9.3

2014-07-01 Thread Mark Kirkwood
On 01/07/14 21:48, Mark Kirkwood wrote: [1] from git://git.postgresql.org/git/users/andresfreund/postgres.git, commits: 4b82477dcaf81ad7b0c102f4b66e479a5eb9504a 10d72b97f108b6002210ea97a414076a62302d4e 67ffebe50111743975d54782a3a94b15ac4e755f fe686ed18fe132021ee5e557c67cc4d7c50a1ada f2378dc2fa5b

Re: [PERFORM] 60 core performance with 9.3

2014-07-01 Thread Mark Kirkwood
On 27/06/14 21:19, Andres Freund wrote: On 2014-06-27 14:28:20 +1200, Mark Kirkwood wrote: My feeling is spinlock or similar, 'perf top' shows kernel find_busiest_group kernel _raw_spin_lock as the top time users. Those don't tell that much by themselves, could you do a hierarchical profile?

Re: [PERFORM] GIST optimization to limit calls to operator on sub nodes

2014-07-01 Thread Pujol Mathieu
Le 30/06/2014 16:04, Tom Lane a écrit : Pujol Mathieu writes: Le 29/06/2014 22:30, Tom Lane a écrit : I don't actually understand what's being requested here that the NotConsistent case doesn't already cover. The NotConsistent case is correctly covered, the sub nodes are not tested because I