| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rajdeep Das <sendrajster(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] PK not being restored |
| Date: | 2009-06-23 13:29:51 |
| Message-ID: | 12975.1245763791@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Rajdeep Das <sendrajster(at)gmail(dot)com> writes:
> For you reference I will list the four tables and a couple of
> functions that has crept in my databases public schema.
These look like you have been restoring an 8.2 or older dump from a
database that had contrib/tsearch2 loaded into it. Please see the
8.3 documentation concerning updating an old tsearch2 installation.
It's not immediately clear why that would have anything to do with
failure to restore PKs, but since you provided no other details,
it's the best advice I have at the moment.
regards, tom lane
PS: this is not a suitable question for -hackers.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barbara Stephenson | 2009-06-23 19:02:30 | tuning our database by increasing shared buffer |
| Previous Message | Rajdeep Das | 2009-06-23 06:05:02 | PK not being restored |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-06-23 14:30:18 | Re: PK not being restored |
| Previous Message | Tom Lane | 2009-06-23 13:25:43 | 8.4RC2 is available |