Tom/Hackers,
Going back a bit, but relevant with 7.3's release...
Tom Lane writes on 03 Sep 2002:
Lee Kindness [EMAIL PROTECTED] writes:
[ original post was regarding the mileage in adding utility
functions to PostgreSQL to cut-out common catalog lookups, thus
making apps less
I have copied Tom's fine email to:
http://www.ca.postgresql.org/docs/momjian/upgrade_7.3
and have added a mention of it in the HISTORY file:
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release. A summary of changes needed in
Was this going to make it into the release notes or something?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane
Sent: Tuesday, 3 September 2002 9:54 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [HACKERS] 7.3 gotchas
Tom, do you think there is millage in adding functions (at least to
contrib) to PostgreSQL to avoid some of the common tasks applications
look into pg_* for?
For example I recently audited our code here for pg_* access, and
managed to create two plpgsql functions to replace all
occurrences. They
Lee Kindness [EMAIL PROTECTED] writes:
CREATE OR REPLACE FUNCTION column_exists(NAME, NAME) RETURNS BOOLEAN AS '
CREATE OR REPLACE FUNCTION table_exists(NAME) RETURNS BOOLEAN AS '
Obviously these need attention when our application targets 7.3 (and
thanks for the heads-up), but all
Bruce suggested that we need a porting guide to help people look for
application and client-library code that will be broken by the changes
in PG 7.3. Here is a first cut at documenting the issues.
Comments welcome --- in particular, what have I missed?
regards, tom lane
