Skip site navigation (1) Skip section navigation (2)

Re: and it's not a bunny rabbit, either

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: and it's not a bunny rabbit, either
Date: 2011-01-02 21:45:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On lör, 2011-01-01 at 17:21 -0500, Robert Haas wrote:
> > I don't see anything wrong with having 20 or 30 messages of variants of
> >
> > "foo cannot be used on bar"
> >
> > without placeholders.
> Well, that's OK with me.  It seems a little grotty, but manageably so.
>  Questions:
> 1. Should we try to include the name of the object?  If so, how?

Hmm.  There is a bit of a difference in my mind between, say,

    constraints cannot be used on sequences

    constraint "foo" cannot be used on sequence "bar"

the latter leaving open the question whether some other combination
might work.

> 2. Can we have a variant with an SQL-command-fragment parameter?
> %s cannot be used on views
> where %s might be CLUSTER, DROP COLUMN, etc.

That's OK; we do that in several other places.

In response to


pgsql-hackers by date

Next:From: Jim NasbyDate: 2011-01-02 22:11:25
Subject: Re: contrib/snapshot
Previous:From: Dimitri FontaineDate: 2011-01-02 21:24:27
Subject: Re: Base Backup Streaming

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group