On Thu, 03 Apr 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
>> Sorry for the delay, but the reply of Tom didn't reach me. I've modified
>> the patch according to Tom's comments. I hope I am not too late.
>
>
es:
> Because of lack of reply from the author, this has been saved for the
> next commit-fest:
>
> http://momjian.postgresql.org/cgi-bin/pgpatches_hold
>
> -------
>
> Tom Lane wrote:
>> Volkan
Hi,
On Sun, 23 Mar 2008, Martin Pihlak <[EMAIL PROTECTED]> writes:
> Attached is a patch that enables tracking function calls through
> the stats subsystem. Original discussion:
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00377.php
>
> Introduces new guc variable - track_functions. P
Hi,
I noticed a small typo in the patch.
prev = palloc((m + n) * sizeof(char));
line should look like
prev = palloc(2 * m * sizeof(char));
instead.
Regards.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map setti
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> Following patch implements configurable penalty costs for levenshtein
> distance metric in fuzzystrmatch contrib module.
Is there a problem with the patch? Would anybody mind helping me to
figure out the reason of this lack of interest, a
4.0.6 distribution for
* inspiration.
+ * Configurable penalty costs extension is introduced by Volkan YAZICI.
*
* metaphone()
* ---
***
*** 116,121
--- 117,158
==
Name
+ levens
On Apr 02 12:37, Tom Lane wrote:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
> > Won't it be better if we distinguish between "default" and "current"
> > value of a parameter with '-' (for the "current") and '+' (for
On Apr 01 07:07, Neil Conway wrote:
> One question about behavior: in the attached patch, omitting an argument
> to \connect or specifying "-" are treated equivalently -- the value for
> that parameter from the previous connection is used, otherwise NULL (for
> the libpq default). Is this what peop
Hi,
I've written do_connect() and \c handling part from scratch in the
attached patch. Here are some features introduced:
- \c syntax is extended. (See comment lines just above \c stuff.)
- do_connect() AI (like used for prompting password or informing
client about connect attempt's result.)
On Feb 11 11:24, Bruce Momjian wrote:
> I have updated the patch to match CVS (attached), but am seeing the
> following regression differences where the COPY error messages are now
> missing.
I've revised the patch (attached) and now it seems to be ok - passes
regression tests too. Any other comme
I've just realized an exception in the sending data while using
PQsendCopyData(). Function's blocking behaviour is not guaranteed,
therefore a
if (PQisnonblocking())
PQsetnonblocking(conn, 0)
kind of phrase required before using PQsendCopyData(). But after a
small investig
Here's a new try. This one touches to pg_dump side too - for v3
COPY functions usage instead of deprecated ones.
I'd be so appreciated if somebody can review attached patch.
Regards.
Index: src/backend/commands/copy.c
===
RCS file:
On Dec 22 01:52, Tom Lane wrote:
> > ! {
> > ! uint64processed = DoCopy((CopyStmt *) parsetree);
> > ! charbuf[21];
> > !
> > ! snprintf(buf, sizeof(buf), UINT64_FORMAT, processed);
> > ! snprintf(completionTag, CO
I tried to prepare a patch for these TODO items:
- Have COPY return the number of rows loaded/unloaded?
- Update [pg_dump and] psql to use the new COPY libpq API.
Added an "uint64 processed" to "struct CopyStateData". It's
incremented each time on a tuple send/receive made by
CopyTo/CopyFrom. Co
I've written a small patch for following TODO item:
«Add GUC variable to run a command on database
panic or smart/fast/immediate shutdown.»
It adds two GUC variables as:
enable_atexit_script_file
atexit_script_file
postmaster will run related script file with passing shutdown type
(like "
On 12/5/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> SELECT * FROM foo WHERE col > 4;
> SELECT * FROM foo WHERE col > 5;
Ofcourse two different SELECT queries are (probably) gonna return
different results. If this is the point you want to underline in the
documentation, just rip that sentence off.
F
On 12/5/05, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Please explain why you think this change is useful.
I've read related part of the documentation 4-5 times and couldn't
figure out the main difference between phantom and nonrepeatable read.
At last, I've googled and found an explanation in
Index: doc/src/sgml/mvcc.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v
retrieving revision 2.53
diff -u -r2.53 mvcc.sgml
--- doc/src/sgml/mvcc.sgml 7 Nov 2005 17:36:44 - 2.53
+++ doc/src/sgml/mvcc.
ter if any
EUC users will try 'em manually too.
On 12/2/05, Bruce Momjian wrote:
> Volkan YAZICI wrote:
> > After Tom's advice (he was doubtful about the patch), while I was
> > thinking about how to improve the spectrum of tests, decided to use
> > src/test/mb. In th
On 12/1/05, Bruce Momjian wrote:
> Where are we on this patch? Is it to be applied?
After Tom's advice (he was doubtful about the patch), while I was
thinking about how to improve the spectrum of tests, decided to use
src/test/mb. In the tests, patch just succeded for unicode and failed
on big5,
On 11/27/05, Volkan YAZICI <[EMAIL PROTECTED]> wrote:
> Tests made on an i686 with a
> 2.6.12.5 kernel. Here's a short list of cases I tried with both latin5
> and unicode charsets:
> - lower/upper functions with Turkish characters.
> - ILIKE matches with both lo
On 11/27/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> > Yes, indeed. I agree with you to find a proper solution for character
> > set handling. But, IMHO, it's better to have a-patchy working system
> > instead of a not working one.
>
> But you just agreed that it doesn't work.
You get me wrong. I tr
On 11/27/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Doesn't this just move the failure cases around?
I don't think so. I've tried to fix every tolower/toupper related
problem (depending on the MB characters) I found in the code. If
there's still a problem with them, it should be related with the
pg
[Sorry if the post is duplicated. But I don't receive and ACK from majordamo.]
On 11/27/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Doesn't this just move the failure cases around?
I don't think so. I've tried to fix every tolower/toupper related
problem (depending on the MB characters) I found in
Last minute edit:
On 11/26/05, Volkan YAZICI <[EMAIL PROTECTED]> wrote:
- In tests it succeeded for Turkish characters while using LATIN5
- encoding. But when encoding is UNICODE it still doesn't work. (IMHO,
- for latin-N encodings there will be no compatibility problems; for
- Unico
Here's small patch to fix case conversion problems for ILIKE and
(Oracle Compat.) lower/upper functions. (Related bug report is here:
http://archives.postgresql.org/pgsql-bugs/2005-10/msg1.php)
In tests it succeeded for Turkish characters while using LATIN5
encoding. But when encoding is UNICO
This is the 4th time sending this patch. Hope this one succeeds.
Index: md5.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/libpq/md5.c,v
retrieving revision 1.30
diff -u -r1.30 md5.c
--- md5.c 17 Oct 2005 16:24:19 -
PQmakeEmptyPGresult() will return NULL if malloc() fails for required
PGresult struct.
Index: doc/src/sgml/libpq.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/libpq.sgml,v
retrieving revision 1.184
diff -u -c -r1.184 libpq.sg
Fixed PQconsumeInput() usage for PQgetCopyData() in libpq.sgml.
(Related mail thread:
http://archives.postgresql.org/pgsql-novice/2005-06/msg00038.php)
Fixed SegFault in PQsendQueryGuts() when user submitted a binary
parameter without size.
And 2 typo fixes.
Index: doc/src/sgml/libpq.sgml
===
29 matches
Mail list logo
