What Adrian is saying is that there is no need for "temporary" indexes. You can create the idxs on a temp table and they get dropped when you drop the table.
Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone-------- Original message --------From: Adrian Klaver <adrian.kla...@aklaver.com> Date: 10/21/2015 14:50 (GMT-05:00) To: Jonathan Vanasco <postg...@2xlp.com>, PostgreSQL mailing lists <pgsql-general@postgresql.org> Subject: Re: [GENERAL] temporary indexes? On 10/21/2015 11:43 AM, Jonathan Vanasco wrote: > I couldn't find any mention of this on the archives... > > Have the project maintainers ever considered extending CREATE INDEX to > support "temporary" indexes like CREATE TEMPORARY TABLE? > > When creating temporary tables for analytics/reporting, I've noticed that I > often need to create (then drop) indexes on regular tables. Temporary > indexes seemed like a natural fit here, so i was wondering if there was any > reason why they're not supported (other than no one wanted it!) Something like this?: aklaver@test=> create temporary table temp_test(id int, fld_1 varchar); CREATE TABLE aklaver@test=> create index temp_idx on temp_test(fld_1); CREATE INDEX aklaver@test=> \d temp_test Table "pg_temp_2.temp_test" Column | Type | Modifiers --------+-------------------+----------- id | integer | fld_1 | character varying | Indexes: "temp_idx" btree (fld_1) > -- Adrian Klaver adrian.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
