To: jweatherman91@alumni.wfu.edu
cc: pgsql-admin@postgresql.org
Subject: Re: PKs without indexes 
In-reply-to: <1303209946.7538.12.camel@darkflame.weatherman.net> 
References: <BANLkTimxxeE_6rt=+5X8VynGUX7rvr51VA@mail.gmail.com>
	<1303209946.7538.12.camel@darkflame.weatherman.net>
Comments: In-reply-to John P Weatherman <jweatherman91@alumni.wfu.edu>
	message dated "Tue, 19 Apr 2011 05:45:46 -0500"
Date: Tue, 19 Apr 2011 11:05:22 -0400
Message-ID: <2006.1303225522@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

John P Weatherman <jweatherman91@alumni.wfu.edu> writes:
> I am attempting to set up slony-i and have run into a minor
> glitch...apparently whoever designed the database I have inherited
> didn't consistently build indexes to go along with Primary Keys, or at
> least that's the error message I have been getting.  I am far from
> confident in my own sqlfu in the catalog tables.  Does anyone have a
> script for identifying tables without indexes that correspond to their
> PKs?  I'm just trying to avoid re-inventing the wheel if I can help it.

At least in Postgres, there is no such animal as a PK (or unique)
constraint without an underlying index.  Maybe you'd better be more
clear about what problem you're having.

			regards, tom lane