pgsql-server/src/backend/commands comment.c

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server/src/backend/commands comment.c
Date: 2003-07-17 20:13:57
Message-ID: 20030717201357.69A59CCAB1@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)svr1(dot)postgresql(dot)org 03/07/17 17:13:57

Modified files:
src/backend/commands: comment.c

Log message:
For COMMENT ON DATABASE where database name is unknown or not the current
database, emit a WARNING and do nothing, rather than raising ERROR.
Per recent discussion in which we concluded this is the best way to deal
with database dumps that are reloaded into a database of a new name.

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2003-07-17 20:14:09 pgsql-server/src/backend/commands Tag: REL7_3_ ...
Previous Message Tom Lane 2003-07-17 16:45:25 pgsql-server/src/backend/access/transam Tag: R ...

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-07-17 21:21:48 I am back
Previous Message Tom Lane 2003-07-17 18:30:50 Re: DB2's row_number()