Re: Re: Partitioning such that key field of inherited tables no longer retains any selectivity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: Partitioning such that key field of inherited tables no longer retains any selectivity
Date: 2014-05-11 16:51:09
Message-ID: 1676.1399827069@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Two approaches:
> 1. Standard virtual column name that, when used, gets rewritten into a
> constant that is stored at the table level.
> 2. A way for a column's value to be defined as a function call.

Recent versions of the SQL spec have a notion of "generated columns"
that I think subsumes both of these concepts. We had a draft patch
awhile back that attempted to implement that feature. It crashed
and burned for reasons I don't recall ... but certainly implementing
an already-standardized feature is more attractive than just inventing
behavior on our own.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2014-05-11 16:56:33 Re: Creating a role with read only privileges but user is allowed to change password
Previous Message Ravi Roy 2014-05-11 15:49:51 Re: Creating a role with read only privileges but user is allowed to change password