[PERFORM] Questions on Tags table schema

2007-07-29 Thread Jay Kang
Hello, I'm currently trying to decide on a database design for tags in my web 2.0application. The problem I'm facing is that I have 3 separate tables i.e. cars, planes, and schools. All three tables need to interact with the tags, so there will only be one universal set of tags for the three table

Re: RES: [PERFORM] select on 1milion register = 6s

2007-07-29 Thread Decibel!
On Sat, Jul 28, 2007 at 10:36:16PM +, Ragnar wrote: > On lau, 2007-07-28 at 17:12 -0300, Bruno Rodrigues Siqueira wrote: > > > where > > > > to_char( data_encerramento ,'-mm') > > between '2006-12' and '2007-01' > > assuming data_encerramento is a date column, try: > WHERE data_encer

RES: RES: [PERFORM] select on 1milion register = 6s

2007-07-29 Thread Bruno Rodrigues Siqueira
Look it EXPLAIN ANALYZE select to_char(data_encerramento,'mm/') as opcoes_mes, to_char(data_encerramento,'-mm') as ordem from detalhamento_bas where data_encerramento = '01/12/2006' GROUP BY opcoes_mes, ordem ORDER BY ordem DESC ***

Re: [PERFORM] select on 1milion register = 6s

2007-07-29 Thread Alvaro Herrera
Scott Marlowe wrote: > On 7/28/07, Bruno Rodrigues Siqueira <[EMAIL PROTECTED]> wrote: > > stats_start_collector = off > > #stats_command_string = off > > #stats_block_level = off > > #stats_row_level = off > > #stats_reset_on_server_start = off > > I think you need stats_row_level on for autovac

Re: RES: RES: [PERFORM] select on 1milion register = 6s

2007-07-29 Thread Decibel!
On Sun, Jul 29, 2007 at 01:44:23PM -0300, Bruno Rodrigues Siqueira wrote: > EXPLAIN > ANALYZE > select >to_char(data_encerramento,'mm/') as opcoes_mes, >to_char(data_encerramento,'-mm') as ordem from detalhamento_bas > where > > data_encerramento >= '01/12/2006' and

Re: RES: RES: [PERFORM] select on 1milion register = 6s

2007-07-29 Thread Decibel!
Please reply-all so others can learn and contribute. On Sun, Jul 29, 2007 at 09:38:12PM -0700, Craig James wrote: > Decibel! wrote: > >It's unlikely that it's going to be faster to index scan 2.3M rows than > >to sequential scan them. Try setting enable_seqscan=false and see if it > >is or not. >