On Fri, Jul 22, 2016 at 4:15 AM, Anton Dignös wrote:
> We would like to contribute to PostgreSQL a solution that supports the query
> processing of "at each time point". The basic idea is to offer two new
> operators, NORMALIZE and ALIGN, whose purpose is to adjust (or split) the
> ranges of tuple
On Sat, Aug 5, 2017 at 6:22 PM, Robert Haas wrote:
> On Sat, Aug 5, 2017 at 4:28 PM, Paul A Jungwirth
> wrote:
>> I don't have an opinion on the urgency of back-porting a fix, but if
>> pg_stop_backup(boolean) allows for inconsistent backups, it does sound
>> like
On Sat, Aug 5, 2017 at 1:28 PM, Paul A Jungwirth
wrote:
> On Sat, Aug 5, 2017 at 7:51 AM, Robert Haas wrote:
>> After refreshing my memory further, I take it back. pg_stop_backup()
>> doesn't even have a second argument on v9.6, so back-porting this fix
>> to 9.6 is a
On Sat, Aug 5, 2017 at 7:51 AM, Robert Haas wrote:
> After refreshing my memory further, I take it back. pg_stop_backup()
> doesn't even have a second argument on v9.6, so back-porting this fix
> to 9.6 is a meaningless thing; there's nothing to fix.
According to the docs at
https://www.postgres
> Also, there seems to be at least some preference
> for excluding partitions by default from the \d listing.
As another user of partitions I'll chime in and say that would be very
nice! On the other hand, with pre-10 partitions you do see all the
child tables with `\d`, so showing declarative par
> The above implementation of "first" aggregate returns the first non-NULL item
> value.
I'm curious what advantages this approach has over these FIRST/LAST
functions from the Wiki?:
https://wiki.postgresql.org/wiki/First/last_%28aggregate%29
Also to get the "first non-null value" you can ap
On Thu, Jun 25, 2015 at 8:06 AM, Tom Lane wrote:
> Paul A Jungwirth writes:
>> I'm interested in adding GiST support for the UUID column type
>> . . . . So I'm curious where this change would go?
> btree_gist, I'd think
Okay, thank you for your answer! I was wo
Hello,
I'm interested in adding GiST support for the UUID column type from
the uuid-ossp extension. This has been requested and attempted before:
http://dba.stackexchange.com/questions/83604/optimizing-postgres-row-overlap-constraints-involving-uuids-and-gist
http://www.postgresql.org/m