From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | reece(at)harts(dot)net |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13899: \det ignores visibility; patch attached |
Date: | 2016-01-29 04:55:11 |
Message-ID: | CAB7nPqQ8bruSyhX6dGGrqB9C5KSeYxJNt7fYfmiRjWA8OMTAhg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jan 29, 2016 at 9:34 AM, <reece(at)harts(dot)net> wrote:
> --- src/bin/psql/describe.c.orig 2016-01-28 16:22:33.782890246 -0800
> +++ src/bin/psql/describe.c 2016-01-28 16:31:08.052200101 -0800
> @@ -4412,7 +4412,8 @@
> "d.objoid = c.oid AND d.objsubid = 0\n");
>
> processSQLNamePattern(pset.db, &buf, pattern, false, false,
> - NULL, "n.nspname", "c.relname", NULL);
> + NULL, "n.nspname", "c.relname",
> + "pg_catalog.pg_table_is_visible(c.oid)");
>
> appendPQExpBufferStr(&buf, "ORDER BY 1, 2;");
Hm. I don't think so, the current behavior looks to be on purpose. \dE
instead can be used to match the visibility with search_path, so I
would rather modify the documentation to mention that \d[Eitstv]
matches the schema visibility in search_path instead and let \det
alone.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Venkata Balaji N | 2016-01-29 04:56:34 | Re: |
Previous Message | reece | 2016-01-29 00:34:30 | BUG #13899: \det ignores visibility; patch attached |