Re: [GENERAL] Notify argument?

From: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] Notify argument?
Date: 2002-03-21 05:19:47
Message-ID: 1016687988.4573.1.camel@jiro
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Thu, 2002-03-21 at 00:16, Tom Lane wrote:
> nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) writes:
> >> If we're going to change the structure anyway, let's fix it to be
> >> independent of NAMEDATALEN.
>
> > Sounds good. If we're making other backwards-incompatible changes to
> > pgNotify, one thing that bugs me about the API is the use of "relname"
> > to refer to name of the NOTIFY/LISTEN condition.
>
> I hear you ... but my proposal only requires a recompile, *not* any
> source code changes. Renaming the field would break client source code.
> I doubt it's worth that.

Okay, that's fair -- I'll leave it as it is.

Cheers,

Neil

--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jean-Michel POURE 2002-03-21 06:51:38 Re: mysql migration
Previous Message Tom Lane 2002-03-21 05:16:52 Re: [GENERAL] Notify argument?

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-03-21 05:51:52 FW: Help with SET NULL/SET NOT NULL
Previous Message Tom Lane 2002-03-21 05:16:52 Re: [GENERAL] Notify argument?