Re: [BUGS] BUG #5662: Incomplete view

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: saera87(at)hotmail(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [BUGS] BUG #5662: Incomplete view
Date: 2010-12-06 12:47:02
Message-ID: 1291639622.10677.12.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On sön, 2010-09-19 at 14:28 -0400, Tom Lane wrote:
> Or maybe we could implement that function, call it like this
>
> CAST((pg_sequence_parameters(c.oid)).max_value AS
> cardinal_number) AS maximum_value,
>
> and plan on optimizing the view when we get LATERAL.

Here is an implementation of that.

I'm not exactly sure if the accesses to the sequence are correctly
locked/unlocked, but it appears to work.

I also revised the definition of the info schema view slightly, after
juggling several more recent SQL standard drafts.

Attachment Content-Type Size
sequence-parameters.patch text/x-patch 7.3 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jorge Augusto Meira 2010-12-06 12:47:53 Re: Problems with max_connections parameter
Previous Message Adrian Klaver 2010-12-05 19:15:34 Re: BUG #5783: plpythonu bool behavior change

Browse pgsql-hackers by date

  From Date Subject
Next Message Boxuan Zhai 2010-12-06 13:17:46 Fwd: new patch of MERGE (merge_204) & a question about duplicated ctid
Previous Message Itagaki Takahiro 2010-12-06 12:06:27 Re: Per-column collation