| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Feature: temporary materialized views |
| Date: | 2019-01-18 01:53:08 |
| Message-ID: | CAKLmikNwMDWcJ9tSRbUWBZwqNxmmjYgXMWoN06_dUSGbxtEFBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
On Thu, Jan 17, 2019 at 2:40 PM Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
> I did some functional testing today and everything seems to work as
> expected other than that the tab completion for psql seems to be missing.
Thanks. I can add those as soon as I figure how. :-)
So what are next steps here besides tab autocompletion? It is OK to
remove that security check? If I understand correctly, there are some
general refactoring of code Tom is proposing, but I am not sure if I
am able to do that/understand that.
Mitar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-01-18 02:46:18 | Shouldn't current_schema() be at least PARALLEL RESTRICTED? |
| Previous Message | Mitar | 2019-01-18 01:50:32 | Re: Feature: temporary materialized views |