Re: exposing pg_controldata and pg_config as functions

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: exposing pg_controldata and pg_config as functions
Date: 2015-09-08 20:22:03
Message-ID: 55EF436B.1000108@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/7/15 7:21 PM, Andrew Dunstan wrote:
> I already gave a use case that you dismissed in favour of a vague
> solution that we don't actually have.

But that's also the only use case so far, which seems a little thin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2015-09-08 20:23:16 ALTER INDEX...SET tab completion
Previous Message Peter Eisentraut 2015-09-08 20:21:12 Re: exposing pg_controldata and pg_config as functions