Yes, libedit is used. On Mac OSX libreadline is a soft link
to libedit, so that's what's used regardless of configure settings.
Here are the version numbers:
$ ll /usr/lib/libreadline.dylib
lrwxr-xr-x 1 root wheel 15 2 Apr 18:51 /usr/lib/libreadline.dylib -
> libedit.2.dylib
$ ll /usr/lib
The following bug has been logged online:
Bug reference: 4398
Logged by: Rainer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3 /b1400
Operating system: Windows XP
Description:Backslashes get escaped despite of backslash_quote=off
Details:
Subject to: Bac
The following bug has been logged online:
Bug reference: 4399
Logged by: Matt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 1.8.4 rev: 7358
Operating system: osX
Description:List of Servers Cleared
Details:
Apologies if already reported, I did read the TODO b
On Thu, Sep 4, 2008 at 1:10 PM, Matt <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4399
> Logged by: Matt
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 1.8.4 rev: 7358
> Operating system: osX
> Description:List of
The following bug has been logged online:
Bug reference: 4400
Logged by: Jan-Peter Seifert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Windows xp Professional
Description:initdb doesn't work with partition D:
Details:
Hello,
wheneve
Rudolf Leitgeb <[EMAIL PROTECTED]> writes:
> Yes, libedit is used. On Mac OSX libreadline is a soft link
> to libedit, so that's what's used regardless of configure settings.
Actually, given that you got compile warnings, the thing to focus on is
probably what readline #include files were used. I
"Rainer" <[EMAIL PROTECTED]> writes:
> Description:Backslashes get escaped despite of backslash_quote=off
Aren't you looking for standard_conforming_strings? backslash_quote is
something else entirely, and doesn't actually do anything at all when
backslash escaping is disabled.
> Two que
Hi!
The reason was a corrupted system library and "sfc /scannow" have helped me.
I wish you remember this solution and will advise it to other people.
Thanks.
--- Исходное сообщение ---
От кого: Zdenek Kotala <[EMAIL PROTECTED]>
Кому: [EMAIL PROTECTED]
Дата: 1 сентября, 19:55
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tom,
Hi list,
(I'm the same as [EMAIL PROTECTED] who started this thread,
this is my regular address, you may compare the gpg-keys if in doubt :)
On 4 Sep 2008 at 11:51, Tom Lane wrote:
>
> Aren't you looking for standard_conforming_strings?
Of
"Rainer Glueck" <[EMAIL PROTECTED]> writes:
> How can backslashes be stopped from escaping themselves in like-statements
Use ESCAPE ''. There isn't any other way provided. I suppose we might
consider inventing a separate GUC parameter to specify what the default
escape sequence is, but we wouldn
The following bug has been logged online:
Bug reference: 4401
Logged by: vinayak
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: CentOS release 5
Description:concurrent updates to a table blocks one update
indefinitely
Details:
There are
"vinayak" <[EMAIL PROTECTED]> writes:
> A single run of this update works as expected. Concurrent runs cause one to
> succeed and the other to be blocked indefinitely.
It's not blocked, it's just doing EvalPlanQual over and over, and that's
quite inefficient in this example. (It looks like it's
12 matches
Mail list logo