| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jweatherman91(at)alumni(dot)wfu(dot)edu |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PKs without indexes |
| Date: | 2011-04-19 15:05:22 |
| Message-ID: | 2006.1303225522@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
John P Weatherman <jweatherman91(at)alumni(dot)wfu(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jerry Sievers | 2011-04-19 15:19:33 | Re: PKs without indexes |
| Previous Message | Kevin Grittner | 2011-04-19 14:00:23 | Re: Orphan Temp Table After PITR |