Decibel! [EMAIL PROTECTED] writes:
On Fri, Jul 27, 2007 at 04:07:01PM +0100, Gregory Stark wrote:
Fwiw, do we really not want to compress anything smaller than 256 bytes
(everyone in Postgres uses the default strategy, not the always strategy).
Is there actually a way to specify always
This small patch makes the syslog pipe use binary mode on Windows so
that CRLF translation (and possibly other oddities) don't upset the pipe
chunking protocol. It preserves text mode for the redirected syslog
file, as recently discussed on -hackers, so there should be no visible
change.
Attached is a patch which implements, as discussed briefly on -hackers, a
user-visible function to get at the information that convert_to_scalar uses to
generate selectivity estimates.
The main use case for this is for tools such as pgadmin which want to make
sense of the histograms, they need
Gregory Stark [EMAIL PROTECTED] writes:
Attached is a patch which implements, as discussed briefly on -hackers, a
user-visible function to get at the information that convert_to_scalar uses to
generate selectivity estimates.
This is an astonishingly bad idea, as it exposes and thereby sets in
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Attached is a patch which implements, as discussed briefly on -hackers, a
user-visible function to get at the information that convert_to_scalar uses
to
generate selectivity estimates.
This is an astonishingly bad
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
This small patch makes the syslog pipe use binary mode on Windows
You need to think harder about where you are inserting the additions,
as these choices seem a bit random.
Is this more to your taste?
cheers
andrew
Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
This small patch makes the syslog pipe use binary mode on Windows
You need to think harder about where you are inserting the additions,
as these choices seem a bit random.
Is this more to your
On 7/27/07, Zdenek Kotala [EMAIL PROTECTED] wrote:
I attach pgcrypto patch which fix two problems on system without strong
crypto support (e.g. default Solaris 10 installation):
1) postgres crashes when AES cipher uses long key
2) Blowfish silently cut longer keys. It could bring problem when
I did my first minimal review of this patch. First, it is massive
26k line diff for the new commands and functionality, and 31k for
adding snowball stemmer. I am glad Oleg and Teodor wrote this because
they have been around this code for a while and are available to fix any
problems we
Teodor Sigaev wrote:
http://www.sigaev.ru/misc/tsearch_core-0.58.gz
Changes since 0.52 version:
1) Introduce dictionary's template which contains only methods of dictionary
and
can be managed only by superuser.
CREATE TEXT SEARCH DICTIONARY dictname
TEMPLATE dicttmplname
10 matches
Mail list logo
