Tom Lane wrote:
> Bruce Momjian writes:
> > Seems there is some inconsistency there. There are two types of
> > function listings, one with just the types, and another with param_name
> > and then type. We use "string" instead of "text" because varchar() and
> > char() can also be used.
>
> Whe
Bruce Momjian writes:
> Seems there is some inconsistency there. There are two types of
> function listings, one with just the types, and another with param_name
> and then type. We use "string" instead of "text" because varchar() and
> char() can also be used.
Where did that come from? The ac
Joachim Wieland wrote:
> Is there any reason, why regexp_replace is not included in the tables of the
> string functions?
>
> http://developer.postgresql.org/docs/postgres/functions-string.html
>
> The appended patch adds regexp_replace() and links to the pattern matching
> section for substring
Is there any reason, why regexp_replace is not included in the tables of the
string functions?
http://developer.postgresql.org/docs/postgres/functions-string.html
The appended patch adds regexp_replace() and links to the pattern matching
section for substring / regexp_replace.
I noticed that in
Patch applied. It will appear in 8.2.
---
Bruce Momjian wrote:
>
> I have implemented the idea I listed below, patch attached.
>
> ---
>
> Bruce Mo
On Wed, 2006-05-17 at 18:17 +0200, Martijn van Oosterhout wrote:
> Persuant to the discussions currently on -hackers, here's a patch that
> uses zlib to compress the tapes as they go to disk. I default to the
> compression level 3 (think gzip -3).
>
> Please speed test all you like, I *think* it's
Persuant to the discussions currently on -hackers, here's a patch that
uses zlib to compress the tapes as they go to disk. I default to the
compression level 3 (think gzip -3).
Please speed test all you like, I *think* it's bug free, but you never
know.
Outstanding questions:
- I use zlib becaus
On Wed, 2006-05-17 at 10:05 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Code changes to separate out the symbol for SLRU_BLCKSZ from standard
> > BLCKSZ. Same reasons as for doing this for XLOG_BLCKSZ.
>
> Have you done any benchmarking that shows this is a good idea?
Som
Simon Riggs <[EMAIL PROTECTED]> writes:
> Code changes to separate out the symbol for SLRU_BLCKSZ from standard
> BLCKSZ. Same reasons as for doing this for XLOG_BLCKSZ.
Have you done any benchmarking that shows this is a good idea?
My own thoughts on the subject have been along the line that pag
Code changes to separate out the symbol for SLRU_BLCKSZ from standard
BLCKSZ. Same reasons as for doing this for XLOG_BLCKSZ.
If no objections, I'll add this to pg_* binaries and the control file
also.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
Index: src/backend/
10 matches
Mail list logo
