From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Josh Kupershmidt <schmiddy(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bugfix: --echo-hidden is not supported by \sf statements |
Date: | 2013-02-27 18:19:03 |
Message-ID: | CAFj8pRAe1PQvfyyHQYRmL7OQDJiPV7OLAFx-1-cQGExw5QK1ug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 결과SQL |
2013/2/27 Stephen Frost <sfrost(at)snowman(dot)net>:
> * Pavel Stehule (pavel(dot)stehule(at)gmail(dot)com) wrote:
>> we cannot use autocomplete or if we use, then more precious code is on
>> server side still - everywhere where function autocomplete is used,
>> then function signature is reparesed again on server side.
>
> This doesn't make any sense to me.
>
> We should rip out the auto-complete that we already have for functions
> because the tab-complete queries the database and then the whole string
> is sent to the server and parsed by it?
autocomplete send a SQL query in every iteration to server - so it is
not any new overhead. And if we should to write some smarted routine,
then I prefer server side due better reusability and better exception
processing than psql environment - and a possibility of access to
system caches and auxiliary functions for arguments processing. This
routine can be smart enough to support autocomplete and unique
identification without needless exceptions - and then psql behave can
be more smooth and consistent.
Regards
Pavel
>
> Thanks,
>
> Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-02-27 18:28:46 | Re: Strange Windows problem, lock_timeout test request |
Previous Message | Tom Lane | 2013-02-27 18:07:02 | Re: Strange Windows problem, lock_timeout test request |