From: Martijn van Oosterhout <kleptog@svana.org>
To: Bruce McAlister <bruce.mcalister@blueface.ie>
Cc: pgsql-general@postgresql.org
Subject: Re: PostgreSQL 8.2.3 VACUUM Timings/Performance
Date: Sun, 18 Mar 2007 17:54:29 +0100
Message-ID: <20070318165429.GD5722@svana.org> (raw)
In-Reply-To: <etepst$18fc$1@news.hub.org>
References: <esh2mg$16vu$1@news.hub.org>
<19106.1173111068@sss.pgh.pa.us>
<esrdsb$1klg$1@news.hub.org>
<etepst$18fc$1@news.hub.org>
On Fri, Mar 16, 2007 at 07:06:57PM -0000, Bruce McAlister wrote:
> Okay, I'm getting a little further now. I'm about to create entries in the
> pg_autovacuum system tables. However, I'm a little confused as to how I go
> about finding out the OID value of the tables. The pg_autovacuum table
> requires the OID of the table you want to create settings for (vacrelid).
> Can anyone shed some light on how I can extract the OID of the table? Also,
> what happens if you create a table without OID's, are you still able to add
> it's details in the pg_autovacuum table if there is no OID associated with a
> table?
The easiest would seem to be to be:
SELECT 'mytable'::regclass;
That will get you the OID without you having to look it up yourself.
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/> From each according to his ability. To each according to his ability to litigate.
Attachments:
signature.asc (application/pgp-signature, 188B) download
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: kleptog@svana.org, bruce.mcalister@blueface.ie, pgsql-general@postgresql.org
Subject: Re: PostgreSQL 8.2.3 VACUUM Timings/Performance
In-Reply-To: <20070318165429.GD5722@svana.org>
* 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