Bruce Momjian wrote:
Jan Wieck wrote:
Attached is a corrected version that solves the query cancel problem by
not napping any more and going full speed as soon as any signal is
pending. If nobody objects, I'm going to commit this tomorrow.
Jan, three questions. First, is this useful now that we
Euler Taveira de Oliveira wrote:
> I have updated postgres and psql translation. If it's not
> inconvenience, apply the postgres in cvs head too.
>
> This is a big file, so I put it here:
> http://www.ufgnet.ufg.br/euler/translation_7_4_pt_BR.tgz
Done. (The host was unreachable last time, so it t
Neil Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I thought llast() and length() were going away too?
> For llast(), I decided to keep it around: it is nicely symmetric
> with linitial(), and it makes any code that actually needs the last
> value in a list significantly more readable.
Tom Lane wrote:
I thought llast() and length() were going away too?
For llast(), I decided to keep it around: it is nicely symmetric
with linitial(), and it makes any code that actually needs the last
value in a list significantly more readable. Since it's a macro
there's no runtime cost.
I had
Neil Conway <[EMAIL PROTECTED]> writes:
> This patch updates the remaining parts of the source tree to use the
> new List API function names and disables the list compatibility API
> by default. This patch compiles without warnings and passes the
> regression tests.
I thought llast() and length
This patch updates the remaining parts of the source tree to use the
new List API function names and disables the list compatibility API
by default. This patch compiles without warnings and passes the
regression tests.
This patch does not remove the usage of FastList; that should also
be done.
