| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Marko Kreen <marko(at)l-t(dot)ee>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: contrib/pgcrypto functions not IMMUTABLE? |
| Date: | 2005-07-04 02:34:10 |
| Message-ID: | 42C8A022.1080901@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Fuhr wrote:
> But if they restore a dump made with pg_dump or pg_dumpall, they'll
> get the old catalog entries sans STRICT, no? People might rebuild
> the module when they upgrade, but they might not think to drop and
> recreate the functions since the definitions are already in the
> dump.
I think it is asking for trouble in general to use the DDL from one
version of pgcrypto with a different version of the pgcrypto
implementation. However, you're right that people are inevitably going
to do this, so I suppose we need to keep the checks. Perhaps it would be
worth adding something to the installation documentation suggesting that
people take care when installing new versions of contrib/ packages and
the like without updating the DDL for those packages.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-04 03:55:51 | HEAD doesn't cope with libraries in non-default locations |
| Previous Message | Bruce Momjian | 2005-07-04 02:29:37 | Re: Constraint Exclusion (Partitioning) - Initial Review |