Steve Woodcock wrote:
> Hi all,
>
> Attached is a patch for the following TODO item:
>
> o Improve psql's handling of multi-line queries
>
> Currently, while \e saves a single query as one entry, interactive
> queries are saved one line at a time. Ideally all queries
> whould be saved lik
Sergey E. Koposov wrote:
> Fix of several issues:
>
> 1) Fix the problems with the \s command.
> When the saveHistory is executed by the \s command we must not do the
> conversion \n -> \x01 (per
> http://archives.postgresql.org/pgsql-hackers/2006-03/msg00317.php )
>
> 2) Fix the handling of
Bruce Momjian writes:
> Does this need any documentation adjustments?
It's pretty useless without any documentation ... which was my original
complaint about it IIRC.
regards, tom lane
---(end of broadcast)---
TIP 4: Have y
- Original Message -
From: "Libor Hohoš" <[EMAIL PROTECTED]>
To: "Tom Lane" <[EMAIL PROTECTED]>
Sent: Wednesday, August 31, 2005 10:06 AM
Subject: Re: [PATCHES] be-secure.c patch
root.crT is file with X509 certificate of Certification Authority
root.crL is file with X509 Certificate
Does this need any documentation adjustments?
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
-
Bruce Momjian wrote:
> Great. Patch applied. I had to adjust your patch around changes made
> to put backslash commands embedded in queries to the top of the history.
I have tested it and it works according to my expectations; the bugs I
noticed are no longer there. Thanks!
It's a bit annoyin
Not from me. I'm not working on it anymore. My work on it was directed
to making unicode work on win32, which was accomplished without ICU.
The original patch was to fix it for FreeBSD. But I think it was put
back pending an actual decision on how to deal with multi-locale
situations, since we'd
On Tue, 2006-03-21 at 17:47 -0500, Tom Lane wrote:
> I'm fairly unconvinced about Simon's underlying premise --- that we
> can't make good use of work_mem in sorting after the run building phase
> --- anyway.
We can make good use of memory, but there does come a point in final
merging where too
