More important than sleep value is the vacuum threshold. If for example
you are expecting to import 5000 rows of data, you can tell
pg_autovacuum to vacuum after every 5000 changes with like
pg_autovacuum -v 5000 -V 0
Matthew
On Wed, 2004-05-19 at 17:09, Carlos wrote:
> Hello Forum,
>
> I wo
On 5/19/04 6:49 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
>> I have a 7.2.1 backend running VACUUM which appears to be blocking all other
>> processes. I have issued SIGTERM and SIGINT directly to that backend and
>> also killed the client process, but the VACUUM continues chewing up CPU and
>> b
On Wednesday May 19 2004 5:49, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I have a 7.2.1 backend running VACUUM which appears to be blocking all
> > other processes. I have issued SIGTERM and SIGINT directly to that
> > backend and also killed the client process, but the VACUUM cont
Bruce Momjian <[EMAIL PROTECTED]> writes:
>>> Hmm. The inet = operator is marked hashable in 7.4 but not in 7.3 ...
>>> I wonder if that is a mistake?
>>
>> Digging further, I find that indeed this seems to be a mistake.
> This has not been fixed yet, right?
Right, it's still on the to-do list.
This has not been fixed yet, right?
---
Tom Lane wrote:
> I wrote:
> > Michael Fuhr <[EMAIL PROTECTED]> writes:
> >> I have a query that works in 7.3.6 but not in 7.4.2 unless I turn
> >> off enable_hashjoin. I'm joining a
"Ed L." <[EMAIL PROTECTED]> writes:
> I have a 7.2.1 backend running VACUUM which appears to be blocking all other
> processes. I have issued SIGTERM and SIGINT directly to that backend and
> also killed the client process, but the VACUUM continues chewing up CPU and
> blocking others.
Hmph.
OK, patch applied. Thanks.
---
Karl O. Pinc wrote:
>
> On 2004.03.31 10:53 Tom Lane wrote:
> > "Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> > > But SQL has 3 valued logic (strictly speaking, not boolean). It
> > > seems t
Sean Shanny <[EMAIL PROTECTED]> writes:
>> I think the problem is not there at all, but with drastic
>> underestimation of the number of rows coming from f_pageviews:
> It does not make sense that the smaller set of values in the IN clause
> would work then does it?
Look at your two plans. In o
Please disregard this thread going forward. I figured it out and feel
all the more stupid for it :)
--Sam
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sam Masiello
Sent: Wednesday, May 19, 2004 1:29 PM
To: Tom Lane
Cc: [EMAIL PROTECTED]
Subject: Re
Tom,
It does not make sense that the smaller set of values in the IN clause
would work then does it?
We took a look at the code we compiled from and indeed the patch you
provided was not not applied, out fault. The patch is in the 7.4.2
code base. We upgraded today and I will be running th
I ran "make" and "make install" which is what I thought the readme said
to do. Did I miss something obvious?
--Sam
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 1:19 PM
To: Sam Masiello
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] Dblink qu
Hi,
is it possible (i am pretty sure) to list the open connections clients
have to a particular database and to force close the connection?
regards David
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Hello Forum,
I would appreciate it if you could recommend settings to use
auto-vacuum in my version 7.4 database. I am uploading several thousands
records in the database at a rate of ~1 second per record (the data is
uploading from a different server). I have noticed that the performanc
On Wed, May 19, 2004 at 12:41:12PM -0400, Christopher Browne wrote:
> This won't happen "implicitly."
>
> tutorial=# CREATE TABLE A (id serial primary key,foo text);
> NOTICE: CREATE TABLE will create implicit sequence "a_id_seq" for "serial" column
> "a.id"
> NOTICE: CREATE TABLE / PRIMARY KEY
"Sam Masiello" <[EMAIL PROTECTED]> writes:
> After trying to insert dblink.sql into the database,
> I just get a series of errors:
> ERROR: stat failed on file '$libdir/dblink': No such file or directory
Did you compile the dblink shared library and install it in the correct
place?
Are there any asynchronous query examples online? I'm especially
interested in event loop integration.
Many TIA!
Mark
--
Mark Harrison
Pixar Animation Studios
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister comma
Sean Shanny <[EMAIL PROTECTED]> writes:
> When I run this against our warehouse instance I get an out of memory
> error. If I remove the
> AND t1.newsletterid_key IN (SELECT newsletterid FROM t_newscontentstatic)
> portion if runs fine.
I think the problem is not there at all, but with drastic
u
After a long battle with technology, [EMAIL PROTECTED] ("Matthew T. O'Connor"), an
earthling, wrote:
> On Wed, 2004-05-19 at 06:02, Peter Haworth wrote:
>> Is it possible/safe to compile the latest version of pg_autovacuum, and use
>> it with a 7.2.4 postmaster?
>>
>> I know the better solution w
Hello all!
I am rather stuck and am hoping someone can help. I am working on a
project where users need to be able to send one query which will hit
databases on multiple hosts (the database structures are the same) and
tie the data back together again.
After doing lots of reading it looks like d
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Florence HENRY) wrote:
> well, almost everything is in the subject !
>
> I have to fill 2 tables (more complicated than in the example !):
>
> CREATE TABLE A (
>id serial primary key,
>foo text);
>
> CREATE TABLE B (
>id ser
Richard Huxton wrote:
Ron St-Pierre wrote:
I am trying to use a sequence value in a function but I keep getting
an error message:
WARNING: Error occurred while executing PL/pgSQL function
correctaddress
WARNING: line 8 at SQL statement
ERROR: column "addressid" is of type integer bu
Marco Lazzeri wrote:
And what about restricting UPDATE/DELETE queries too. Can I still use
VIEWs?
No but that you could use a function for.
Sincerely,
Joshua D. Drake
Bye
Il mer, 2004-05-19 alle 05:06, Joshua D. Drake ha scritto:
You could use a view and give group rights to a particular view.
Jo
I have a 7.2.1 backend running VACUUM which appears to be blocking all other
processes. I have issued SIGTERM and SIGINT directly to that backend and
also killed the client process, but the VACUUM continues chewing up CPU and
blocking others. I know we need an upgrade; does anyone know how I
I'd like to do something like
grant all on * to username;
on a whole database, where * are tables, sequences etc...
is there any shortcut?
thx
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "u
On Wed, 2004-05-19 at 06:02, Peter Haworth wrote:
> Is it possible/safe to compile the latest version of pg_autovacuum, and use
> it with a 7.2.4 postmaster?
>
> I know the better solution would be to upgrade everything, but that involves
> a lot of work which we've managed to put off for a long t
Is it possible/safe to compile the latest version of pg_autovacuum, and use
it with a 7.2.4 postmaster?
I know the better solution would be to upgrade everything, but that involves
a lot of work which we've managed to put off for a long time already, and
autovacuum is pretty much the only feature
Ron St-Pierre wrote:
I am trying to use a sequence value in a function but I keep getting an
error message:
WARNING: Error occurred while executing PL/pgSQL function
correctaddress
WARNING: line 8 at SQL statement
ERROR: column "addressid" is of type integer but expression is of
ty
Tom Lane wrote:
Nikola Milutinovic <[EMAIL PROTECTED]> writes:
[ about NaN on Tru64 ]
This compiles on Tru64 4.0D (the compiler swallows it), but fails on
Tru64 UNIX 5.1B. Both basic CC and DTK Compaq CC break on that file
complaining on that constant evaluation. The best way to solve it is to
u
28 matches
Mail list logo
