From: Pierre C <lists@peufeu.com>
To: Mario Splivalo <mario.splivalo@megafon.hr>
Cc: pgsql-performance@postgresql.org
Subject: Re: SELECT INTO large FKyed table is slow
Date: Sun, 28 Nov 2010 22:50:42 +0100
Message-ID: <op.vmwhmsepeorkce@apollo13> (raw)
In-Reply-To: <4CF2A8A6.4010400@megafon.hr>
References: <4CF24103.8030209@megafon.hr>
<op.vmv9j3oneorkce@apollo13>
<4CF2A8A6.4010400@megafon.hr>
> I pasted DDL at the begining of my post.
Ah, sorry, didn't see it ;)
> The only indexes tables have are the ones created because of PK
> constraints. Table drones has around 100k rows. Table drones_history has
> around 30M rows. I'm not sure what additional info you'd want but I'll
> be more than happy to provide more relevant information.
Can you post the following :
- pg version
- output of VACCUM ANALYZE VERBOSE for your 2 tables
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: lists@peufeu.com, mario.splivalo@megafon.hr
Subject: Re: SELECT INTO large FKyed table is slow
In-Reply-To: <op.vmwhmsepeorkce@apollo13>
* 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