From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: delete and select with IN clause issues
Date: Fri, 03 Nov 2006 01:58:08 -0500
Message-ID: <27200.1162537088@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0611022239120.6160@discord.home.frostconsultingllc.com>
References: <Pine.LNX.4.64.0611021541050.29554@discord.home.frostconsultingllc.com>
<24512.1162525800@sss.pgh.pa.us>
<Pine.LNX.4.64.0611022021150.6160@discord.home.frostconsultingllc.com>
<26796.1162535008@sss.pgh.pa.us>
<Pine.LNX.4.64.0611022239120.6160@discord.home.frostconsultingllc.com>
Jeff Frost <jeff@frostconsultingllc.com> writes:
> BTW, just to make sure I get the right file to ship over if we have this
> again, it would be: /var/lib/pgsql/data/base/9366228/16204210 yes?
Not necessarily --- the filename is initially the same as the index OID,
but it wouldn't be anymore after a REINDEX. Instead use what you get from
select relfilenode from pg_class where relname = 'page_view_visit_idx';
and note you will need to recheck it after reindexing.
Also, it's a good idea to do CHECKPOINT right before copying the
physical file, to make sure you've got a consistent file image on-disk.
If you want to be 100% certain, shut down the postmaster while copying,
but unless the index file is pretty large I think that's not necessary.
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, jeff@frostconsultingllc.com
Subject: Re: delete and select with IN clause issues
In-Reply-To: <27200.1162537088@sss.pgh.pa.us>
* 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