Alvaro Herrera wrote:
"These settings control the default behavior for the autovacuum daemon.
Please refer to _Section 22.1.4_ for more information."
I don't see how to cleanly fit "The auto-vacuum daemon" in that sentence
in a way that looks like a reference.
So, in short, if there is a policy
On Mon, Sep 12, 2005 at 04:17:29PM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I have prepared some docs for autovacuum. I attach the patch. Comments
> > on grammar, style etc. are welcome.
Applied, updated per your comments.
> > +See .
>
> I think we mostly don
Tom Lane wrote:
+ Additionally to the base threshold values and scale factors, there are
+ two parameters that can be set for each table in pg_autovacuum:
"Additionally to" is not good style ... maybe "Besides"?
I think "In addition to" was what Alvaro meant, which works.
Neil Conway wrote:
This patch is blocking other work [...]
Otherwise I'll apply it this evening (EST).
Applied.
-Neil
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I have prepared some docs for autovacuum. I attach the patch. Comments
> on grammar, style etc. are welcome.
A few piddling suggestions:
> +See .
I think we mostly don't use endterm on cross-references to sections.
Not sure if that's a project s
Neil Conway <[EMAIL PROTECTED]> writes:
> Seth Robertson wrote:
>> Instead of writing a utility to replicate the functionality in
>> pg_dump, I created a new flag, --where, which allows you to postpend
>> where (or order or limit or whatever) sql fragments at the end of the
>> select done by pg_dum
Michael Fuhr wrote:
The synopsis for SPI_getbinval() shows the third argument being
"colnumber" but in the Arguments section it appears as "rownumber."
This patch corrects that.
Thanks for the patch -- applied to HEAD, 8.0, and 7.4
-Neil
---(end of broadcast)--
Seth Robertson wrote:
In order to support some automation, I needed the ability to pull out
subsets of postgres tables in a format which could be loaded into
other postgres databases.
One alternative would be using CREATE TABLE AS to create a separate
table containing the desired subset, and t
David Fetter wrote:
***
*** 173,179
Integrating autovacuum into the server allows it to be
automatically started and stopped in sync with the database
server, and allows autovacuum to be configured from
! postgresql.conf.
Peter Eisentraut wrote:
Moreover, I don't agree with the premise.
This patch is blocking other work. If you still object to it, can you
elaborate why?
Otherwise I'll apply it this evening (EST).
-Neil
---(end of broadcast)---
TIP 3: Have you
1. Why did you base the datatype on cstring? That's inappropriate for
anything except guaranteed-short strings, because it's not toastable.
It's only my laziness. I can adapt patch for TEXT. It's only temporary
solution. The goal is true xml type.
2. Is it really necessary to hack up the g
Alvaro Herrera wrote:
> I have prepared some docs for autovacuum. I attach the patch.
> Comments on grammar, style etc. are welcome.
Looks very good to me.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP
Hackers,
I have prepared some docs for autovacuum. I attach the patch. Comments
on grammar, style etc. are welcome.
I will not apply it yet because it conflicts with Neil's runtime-config
restructuring, so I'll wait until he applies his patch.
--
Alvaro Herrera -- Valdivia, Chile Arch
Tom Lane wrote:
Is it really necessary to hack up the grammar for this? Seems like
you should create ordinary functions to manipulate the datatype(s).
If every datatype thought it could do this sort of thing, we'd have
a completely unmanageable grammar.
Can we do variadic functions with
Am Montag, 12. September 2005 16:05 schrieb Tom Lane:
> 2. Is it really necessary to hack up the grammar for this?
Yes, because the syntax defined in the SQL standard is completely weird.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)-
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> This patch contains SQL/XML public function XMLFOREST, XMLELEMENT, ... based
> on CString type. This patch hasn't high quality, but can be usefull for
> testing funcionality, and maybe for some people.
1. Why did you base the datatype on cstring? Th
On Sat, Aug 13, 2005 at 09:01:45AM -0600, Michael Fuhr wrote:
> If no statements have been executed in this transaction then committed
> is true, so ECPGtrans() ignores the current statement. It looks
> like the code should make an extra consideration for SAVEPOINT in
> case it's the first stateme
Hello
This patch contains SQL/XML public function XMLFOREST, XMLELEMENT, ... based
on CString type. This patch hasn't high quality, but can be usefull for
testing funcionality, and maybe for some people. Patch needs initdb and
following registration:
CREATE AGGREGATE pg_catalog.fast_cstring_
18 matches
Mail list logo
