On Wed, Jun 8, 2016 at 7:06 AM, Alvaro Herrera wrote:
> Michael Paquier wrote:
>> On Thu, Jun 2, 2016 at 3:42 PM, Michael Paquier
>> wrote:
>> > On Thu, Jun 2, 2016 at 1:00 PM, Michael Paquier
>> > wrote:
>> >> I
Michael Paquier wrote:
> On Thu, Jun 2, 2016 at 3:42 PM, Michael Paquier
> wrote:
> > On Thu, Jun 2, 2016 at 1:00 PM, Michael Paquier
> > wrote:
> >> I have added an open item for 9.6 regarding this patch, that would be
> >> good to complete
On Tue, Jun 7, 2016 at 7:35 AM, Alvaro Herrera wrote:
> In looking at the DROP ACCESS METHOD completion I noticed that the
> words_after_create gadget is a bit buggy: for things with more than one
> word in the thing name (such as MATERIALIZED VIEW, USER MAPPING FOR,
>
Michael Paquier wrote:
> On Thu, Jun 2, 2016 at 3:42 PM, Michael Paquier
> wrote:
> > On Thu, Jun 2, 2016 at 1:00 PM, Michael Paquier
> > wrote:
> >> I have added an open item for 9.6 regarding this patch, that would be
> >> good to complete
Noah Misch wrote:
> The above-described topic is currently a PostgreSQL 9.6 open item. Álvaro,
> since you committed the patch believed to have created it, you own this open
> item. If some other commit is more relevant or if this does not belong as a
> 9.6 open item, please let us know.
On Thu, Jun 02, 2016 at 04:00:33PM +0900, Michael Paquier wrote:
> On Thu, Jun 2, 2016 at 3:42 PM, Michael Paquier
> wrote:
> > On Thu, Jun 2, 2016 at 1:00 PM, Michael Paquier
> > wrote:
> >> I have added an open item for 9.6 regarding this
On Thu, Jun 2, 2016 at 3:42 PM, Michael Paquier
wrote:
> On Thu, Jun 2, 2016 at 1:00 PM, Michael Paquier
> wrote:
>> I have added an open item for 9.6 regarding this patch, that would be
>> good to complete this work in this release for
On Thu, Jun 2, 2016 at 1:00 PM, Michael Paquier
wrote:
> I have added an open item for 9.6 regarding this patch, that would be
> good to complete this work in this release for consistency with the
> other objects.
Doh. I forgot to update psql --help.
--
Michael
From
On Wed, Jun 1, 2016 at 8:25 PM, Teodor Sigaev wrote:
As far as I can see, COMMENT ON has no support for access methods.
Wouldn't we want to add it as it is created by a command? On top of
that, perhaps we could have a backslash command in psql to list the
As far as I can see, COMMENT ON has no support for access methods.
Wouldn't we want to add it as it is created by a command? On top of
that, perhaps we could have a backslash command in psql to list the
supported access methods, like \dam[S]? The system methods would be in
this case all the
On Wed, Jun 1, 2016 at 4:52 AM, Robert Haas wrote:
> On Fri, May 27, 2016 at 7:53 AM, Michael Paquier
> wrote:
>> As far as I can see, COMMENT ON has no support for access methods.
>> Wouldn't we want to add it as it is created by a command? On
On Fri, May 27, 2016 at 7:53 AM, Michael Paquier
wrote:
> As far as I can see, COMMENT ON has no support for access methods.
> Wouldn't we want to add it as it is created by a command? On top of
> that, perhaps we could have a backslash command in psql to list the
>
Michael Paquier writes:
> As far as I can see, COMMENT ON has no support for access methods.
> Wouldn't we want to add it as it is created by a command? On top of
> that, perhaps we could have a backslash command in psql to list the
> supported access methods, like
Hi all,
As far as I can see, COMMENT ON has no support for access methods.
Wouldn't we want to add it as it is created by a command? On top of
that, perhaps we could have a backslash command in psql to list the
supported access methods, like \dam[S]? The system methods would be in
this case all
14 matches
Mail list logo