Hello
I have problem with sending propably too much large patch, so I am sending
only link to patch. Is it correct? I sent this patch two times without
success. This patch add new PL language to PostgreSQL. You can enable it by
setting --with-sqlpsm in configure.
Proposal: http://archives.po
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> [ make CLUSTER skip WAL when possible ]
Applied with some editorialization.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Jeremy Drake wrote:
I just realized that the last patch removed all usage of fcinfo in the
setup_regexp_matches function, so this version of the patch also removes
it as a parameter to that function.
Applied, thanks.
-Neil
---(end of broadcast)
Marko Kreen wrote:
Replace 4-clause licensed blf.[ch] with blowfish implementation
from PuTTY with is under minimal BSD/MIT license.
Applied -- thanks for the patch.
-Neil
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL proj
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.
---
Je
Index: src/doc/src/sgml/ref/cluster.sgml
===
*** src.orig/doc/src/sgml/ref/cluster.sgml 2007-03-28 23:02:12.0
+0200
--- src/doc/src/sgml/ref/cluster.sgml 2007-03-28 23:03:14.0 +0200
***
*** 20,27 ***
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.
---
Pa
> Huh?
You're right. I should have done a "quilt refresh -c" before re-posting the
patch.
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes d
FWIW you don't need to patch the TODO files. They will be updated by
Bruce. (And in any case we don't remove the entries, but rather mark
them with a "-" meaning "done for the next release").
Also, sql_help.h is a generated file. You need to change the appropiate
SGML source (doc/src/sgml/ref/c
Index: src/doc/TODO
===
*** src.orig/doc/TODO 2007-03-27 21:18:01.0 +0200
--- src/doc/TODO2007-03-27 21:18:26.0 +0200
***
*** 624,631
o %Add VERBOSE option to report tables as they
> +1 ... AFAIR there was 0 discussion of the exact syntax before,
> so I don't feel wedded to ORDER BY.
A changed patch comes with the next e-mail.
I can not create a patch for "CLUSTER table USING col1,col2,col3",
because I'm not yet deep into postgresql and don't have the time
for that. I just
> Jeremy Drake wrote:
> > On Thu, 22 Mar 2007, Tom Lane wrote:
> >
> > > I'd vote for making this new code look like the rest of it, to wit
> > > hardwire the values.
> >
> > Attached please find a patch which does this.
I just realized that the last patch removed all usage of fcinfo in the
setup_
This is the most recent email I have on this. Was the scrollable patch
applied? If not, would you resubmit?
I resubmit scrollable cursor patch
Regards
Pavel Stehule
_
Emotikony a pozadi programu MSN Messenger ozivi vasi konver
On Wed, 2007-03-28 at 09:39 -0400, Alvaro Herrera wrote:
> What other auxiliary processes are you envisioning, anyway?
WAL Writer, multiple bgwriters, checkpoint process, parallel query and
sort slavesplus all the ones I haven't dreamed of yet.
No need to agree with my short list, but we do s
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Though I don't think we're implementing "CLUSTER table ORDER BY col1,
> col2" anytime soon, ORDER BY does imply that a list of columns is to
> follow. How about "CLUSTER table USING index"?
+1 ... AFAIR there was 0 discussion of the exact syntax b
Simon Riggs wrote:
> On Tue, 2007-03-27 at 17:41 -0400, Alvaro Herrera wrote:
>
> > The main change is to have an array of Worker structs in shared memory;
> > each worker checks the current table of all other Workers, and skips a
> > table that's being vacuumed by any of them. It also rechecks t
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Some comments on the patch below.
Thanks!
> Gregory Stark wrote:
>
>
>
> The comment claims that we use heap sort when the user says he doesn't want to
> use glibc's qsort. I recall that we always use our own qsort implementation
> nowadays. And
On Wed, 2007-03-28 at 10:54 +0900, Koichi Suzuki wrote:
> As written below, full page write can be
> categolized as follows:
>
> 1) Needed for crash recovery: first page update after each checkpoint.
> This has to be kept in WAL.
>
> 2) Needed for archive recovery: page update between pg_start_b
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
"Holger Schurig" <[EMAIL PROTECTED]> writes:
* psql tab-completion, it favours now CLUSTER table ORDER BY index"
It occurs to me (sorry that I didn't think of this earlier) that if we're
going to use "ORDER BY" it really ought to take
Some comments on the patch below.
Gregory Stark wrote:
+ /* tuplesort_set_bound - External API to set a bound on a tuplesort
+ *
+ * Must be called before inserting any tuples.
+
+ * Sets a maximum number of tuples the caller is interested in. The first
+ * tuples are maintained using a
On Wed, Mar 28, 2007 at 10:23:09AM +0900, ITAGAKI Takahiro wrote:
> Here are two small code clean-up in initdb and win32_shmem.
>
> pg_char_to_encoding() was redundant in initdb because
> pg_valid_server_encoding() returns the same result if the encoding is valid,
>
> Changes in win32_shmem suppr
21 matches
Mail list logo
