From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: psql tab completion for updatable foreign tables |
Date: | 2013-07-11 06:57:32 |
Message-ID: | CAEZATCVvU-_1XKK7HT_CgydgYGL6RGpoxNiv26c4JC=chP2KnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11 July 2013 00:03, Bernd Helmle <mailings(at)oopsware(dot)de> wrote:
>
>
> --On 8. Juli 2013 16:04:31 +0000 Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
> wrote:
>
>> * pg_relation_is_updatable is only available in 9.3, whereas psql may
>> connect to older servers, so it needs to guard against that.
>>
>
> Oh of course, i forgot about this. Thanks for pointing out.
>
>
>> * If we're doing this, I think we should do it for auto-updatable
>> views at the same time.
>>
>> There was concern that pg_relation_is_updatable() would end up opening
>> every relation in the database, hammering performance. I now realise
>> that these tab-complete queries have a limit (1000 by default) so I
>> don't think this is such an issue. I tested it by creating 10,000
>> randomly named auto-updatable views on top of a table, and didn't see
>> any performance problems.
>>
>> Here's an updated patch based on the above points.
>
>
> Okay, are you adding this to the september commitfest?
>
OK, I've done that. I think that it's too late for 9.3.
Regards,
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Samrat Revagade | 2013-07-11 07:05:43 | Re: [PATCH] big test separation POC |
Previous Message | Fabien COELHO | 2013-07-11 06:23:15 | Re: pgbench patches |