pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Luiz K. Matsumura <luiz@planit.com.br>
Cc: pgsql-performance@postgresql.org
Subject: Re: Optimizing queries that use temporary tables
Date: Tue, 22 Jan 2008 14:34:15 -0600
Message-ID: <dcc563d10801221234j3ca441ebs2aee2da9165d1ca3@mail.gmail.com> (raw)
In-Reply-To: <479644C1.4070703@planit.com.br>
References: <479644C1.4070703@planit.com.br>

On Jan 22, 2008 1:32 PM, Luiz K. Matsumura <luiz@planit.com.br> wrote:
> Hello,
>
> I'm developing some routines that will use temporary tables and need
> advice on how to not lose performance.
>
> I will insert data in a temporary table and use this data to generate
> new sets that will update or add to the same temporary table.
>
> I have some questions that I'm concerned about:
>
> - I can create indexes on this temp table to optimize queries ?

Yes

> If yes...
> - This indexes will be destroyed together (automatic?) the temp table
> when the connection is closed ?

Yes

> - When I insert a lot of new rows, need to run analyze on this temporary
> table ?

Yes



view thread (2+ messages)

Message-ID: <dcc563d10801221234j3ca441ebs2aee2da9165d1ca3@mail.gmail.com>
Permalink:  ../dcc563d10801221234j3ca441ebs2aee2da9165d1ca3@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10801221234j3ca441ebs2aee2da9165d1ca3@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, luiz@planit.com.br
  Subject: Re: Optimizing queries that use temporary tables
  In-Reply-To: <dcc563d10801221234j3ca441ebs2aee2da9165d1ca3@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox