Re: Proposal: variant of regclass

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: variant of regclass
Date: 2013-12-05 11:20:12
Message-ID: CAFj8pRBaEX9K-0JLJveQFX7MQnrLr3ztV98TWKh+y5RWrZK6jA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/12/5 Andres Freund <andres(at)2ndquadrant(dot)com>

> On 2013-12-05 11:54:20 +0100, Pavel Stehule wrote:
> > 2013/12/5 Andres Freund <andres(at)2ndquadrant(dot)com>
> > We can introduce some assert polymorphic function
> >
> > CREATE OR REPLACE FUNCTION notnull(any, message text) RETURNS any, that
> can
> > be used for check inside SQL
>
> Uh. How is that going to help applications that upgraded, without having
> noticed a pretty obscure notice in the release notes?
>

this function doesn't replace a "obscure notice in the release notes".

On second hand is better to throw unpractically designed feature early
than hold it forever.

If there was not too aversion against GUC, I can say, so for some time GUC
can be solution. But it isnot

Regards

Pavel

>
> If this were day one, I would agree we should go that way, but today...
>
> Greetings,
>
> Andres Freund
>
> --
> Andres Freund http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-12-05 11:39:38 Re: better atomics - v0.2
Previous Message Andres Freund 2013-12-05 11:18:44 Re: Proof of concept: standalone backend with full FE/BE protocol