Re: [PERFORM] postgresql.conf recommendations

2013-02-11 Thread Will Platnick
> We will probably tweak this knob some more -- i.e., what is the sweet spot > between 1 and 100? Would it be higher than 50 but less than 100? Or is it > somewhere lower than 50? > > I would love to know the answer to this as well. We have a similar situation, pgbouncer with transaction log

Re: [PERFORM] postgresql.conf recommendations

2013-02-11 Thread Scott Marlowe
On Mon, Feb 11, 2013 at 7:57 AM, Charles Gomes wrote: > > >> Date: Sat, 9 Feb 2013 14:03:35 -0700 > >> Subject: Re: [PERFORM] postgresql.conf recommendations >> From: scott.marl...@gmail.com >> To: jeff.ja...@gmail.com >> CC: charle...@outlook.com; strahin...@nordeus.com; kgri...@ymail.com; >> joh

Re: [PERFORM] postgresql.conf recommendations

2013-02-11 Thread Johnny Tan
On Sat, Feb 9, 2013 at 2:37 PM, Josh Krupka wrote: > Johnny, > > Sure thing, here's the system tap script: > > Thank you for this! > - I think you already started looking at this, but the linux dirty memory > settings may have to be tuned as well (see Greg's post > http://notemagnet.blogspot.c

Re: [PERFORM] Partition insert trigger using C language

2013-02-11 Thread Ali Pouya
Hi Matheus, I try to use your partition_insert_trigger_spi.c code for testing SPI partitionning. But at execution time the *trigdata->tg_trigger->tgargs* pointer is null. Do you know why ? Thanks a lot Best Reagrds Ali Pouya 2013/1/11 Matheus de Oliveira > > On Fri, Jan 11, 2013 at 8:19 AM, Hei

Re: [PERFORM] postgresql.conf recommendations

2013-02-11 Thread Charles Gomes
> Date: Sat, 9 Feb 2013 14:03:35 -0700 > Subject: Re: [PERFORM] postgresql.conf recommendations > From: scott.marl...@gmail.com > To: jeff.ja...@gmail.com > CC: charle...@outlook.com; strahin...@nordeus.com; kgri...@ymail.com; > johnnyd...@gmail.com; a...@hsk.hk; jkru...@gmail.com; a...@paperles

[PERFORM] Is it correct to optimize a query with subselect in the "where"?

2013-02-11 Thread Alexandre Riveira
I managed to optimize the query below, adding a subselect (is disabled) after the "where" it would be correct? EXPLAIN (ANALYZE, BUFFERS) SELECT CONCAT_WS(' # ', CONCAT_WS(' ', produto.descricao, produto_watts.descricao, produto_serie.descricao, produto_tecnologia.descricao, produto_modelo.des