| From: | Andrew Biagioni <andrew(dot)biagioni(at)e-greek(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Rod Taylor <rbt(at)rbt(dot)ca>, "Kuhn, Dylan K (4520500D)" <Dylan(dot)Kuhn(at)navy(dot)mil>, pgsql-admin(at)postgresql(dot)org, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] problems with pg_restore |
| Date: | 2003-07-16 22:37:52 |
| Message-ID: | 3F15D3C0.4060707@e-greek.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Tom Lane wrote:
>Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
>
>
>>On Tue, Jul 15, 2003 at 04:03:13PM -0400, Tom Lane wrote:
>>
>>
>>>Given the current implementation, it seems like there are three possible
>>>behaviors for COMMENT ON DATABASE when the database name isn't the same
>>>as the current database:
>>>
>>>
>
>
>
>>There's a fourth possibility: ignore the command and issue a WARNING.
>>
>>
>
>Hmm, that seems like a reasonable choice. Anyone have an objection?
>
My personal experience would lead me to believe that this is the best
option. Count it a vote in favor.
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
Andrew Biagioni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilan Arumainathan | 2003-07-16 22:52:32 | Database migration |
| Previous Message | Tom Lane | 2003-07-16 14:41:39 | Re: [HACKERS] problems with pg_restore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ivan | 2003-07-16 22:48:51 | Re: perm question |
| Previous Message | Tom Lane | 2003-07-16 22:15:17 | Re: perm question |