Hi all,
I use suse and
postgres7.0.
Do we have any rule to set
buffer and other thing of postmaster?
postmaster -N 128 -B 256 -D
/postgres/data
What do the above settings
mean?
TIA
Regards,
Lonh
On Mon, 22 Apr 2002, Jeremy Buchmann wrote:
> Databases are I/O bound...if your I/O is slow, your database will be slow.
> So your goal is to minimize the amount of I/O needed and the time it takes
> to do the I/O. You minimize the amount of I/O by getting things with big
> caches.
Assuming you
Hello all,
If any one knows of any Postgresql conferences coming up in Australia
could they please let me know the details.
Aaron.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Mon, Apr 22, 2002 at 04:32:37PM -0400, Tom Lane wrote:
> It'll be interesting to see how the plans change depending on whether
> you are searching for a judge or not ...
A whole new meaning to judge shopping, err, searching?
Ross
---(end of broadcast)-
[EMAIL PROTECTED] wrote:
> Hello, :-)
>
> Can someone help me spec out the hardware needed for a simple web-based
> database app?
>
> Basically, that application needs to lookup a single row by its primary key.
> This would be fairly straightforward, except that the table needs to contain
> up
"Nick Fankhauser" <[EMAIL PROTECTED]> writes:
> In this case, we've got an unusual distribution that looks like this:
> Among the actors to which cases may be assigned:
> The State gets 10% of the cases
> 8 Judges get 3.5% of the cases each
> 50 Attorneys get about 0.1% each
> The remaining 388,
> In the "after" case you are showing "18105XS" as the most common
> actor_id, with a frequency of 11.2% of the entries. Where'd that
> come from? Is it correct?
I believe this is correct, and the reason I've not been getting poor
performance on the old database is that the stats are not up to
Denny-Schierz <[EMAIL PROTECTED]> writes:
> testlinux:/home/amphora2/inst# su www-data -s /bin/bash -c 'psql amphora2 <
>amphora2.0.dump'
> psql: FATAL 1: IDENT authentication failed for user "www-data"
> localamphora2 ident amphora
> localall
On Mon, 2002-04-22 at 12:32, Denny-Schierz wrote:
> Hi pgsql-admin,
>
> i want to install the amphora2 light groupware software under Debian Woody
> with pgsql 7.2.1. I have to restore a dump into the amphora2 DB that
> i created before.:
> -
> testlinux:/home/amphora2/inst# su
Guten Tag pgsql-admin,
sorry, for my first mail, i pressed the wrong button, here the full
mail:
i want to install the amphora2 light groupware software under Debian Woody
with pgsql 7.2.1. I have to restore a dump into the amphora2 DB that
i created before.:
-
testlinu
"Nick Fankhauser" <[EMAIL PROTECTED]> writes:
> The "Before" database:
> attname | attdispersion | starelid | staattnum | staop |
> stanullfrac | stacommonfrac | stacommonval | staloval |
> stahival
> --+---+--+
Hi pgsql-admin,
i want to install the amphora2 light groupware software under Debian Woody
with pgsql 7.2.1. I have to restore a dump into the amphora2 DB that
i created before.:
-
testlinux:/home/amphora2/inst# su www-data -s /bin/bash -c 'psql amphora2 <
amphora2.0.dump'
--
> select attname,attdispersion,s.*
> from pg_statistic s, pg_attribute a, pg_class c
> where starelid = c.oid and attrelid = c.oid and staattnum = attnum
> and relname = 'actor_case_assignment';
>
> in each database?
Here are the results:
The "Before" database:
attname | attd
"Nick Fankhauser" <[EMAIL PROTECTED]> writes:
>> Offhand I would think that 7.2 is smart enough to deal with this
> We're on 7.1.3.
Hmm... I don't see why it would make any difference in 7.1
either. You weren't by any chance selecting on the most common
actor_id were you? Really 7.1 only has
> Could we see the queries? (No, I do not remember your view definitions.)
Sure! I'll append the details below. (I was hoping we had correctly guessed
the cause & you wouldn't need details...)
> Offhand I would think that 7.2 is smart enough to deal with this
We're on 7.1.3. We're working to
"Nick Fankhauser" <[EMAIL PROTECTED]> writes:
> So on every primary & foreign key, I have executed this update:
> update table set key = '18105'||key;
> Now, a few queries that used to be swift are very slow,
Could we see the queries? (No, I do not remember your view definitions.)
Offhand I wou
Hello-
Does analyze consider the entire key when creating statistics for a table,
or a substring composed of the leading chars?
Some background:
I've just modified *all* of the keys on my database by prefixing them with
the same source_id that is 5 chars long. This is in preparation for merging
On Sunday 21 April 2002 09:35, Gunnar wrote:
> I'm having problems connecting to my postgresql 7.2.1 running on my Debian
> Linux box.
>
> (as root)
> $ psql template1 foobar
> psql: FATAL 1: IDENT authentication failed for user "foobar"
>
> Could anybody tell me what the problem is?
> The user "
Gunnar-
It looks to me like the two lines in pg_hba conflict, and the first one is
being used. Since you are logged in as root, it looks for "sameuser" on
foobar and doesn't get a match.
Try either logging into linux as foobar or eliminate the first line of
pg_hba.
-Nick
--
Yes,
It's replication which is what i'm talking about
Jules Alberts wrote:
On 18 Apr 2002 at 15:40, Rommel B. Abaya wrote:
> Hi,
>
> I'm trying to find out if database mirroring could be done with
> PostgreSQL. What i mean is that when my applications
> insert/delete/update records in my produc
Hello, :-)
Can someone help me spec out the hardware needed for a simple web-based
database app?
Basically, that application needs to lookup a single row by its primary key.
This would be fairly straightforward, except that the table needs to contain
up to 15 million records. Each row will con
I'm having problems connecting to my postgresql 7.2.1 running on my Debian
Linux box.
(as root)
$ psql template1 foobar
psql: FATAL 1: IDENT authentication failed for user "foobar"
Could anybody tell me what the problem is?
The user "foobar" is created with the createuser command without any p
--On lundi 22 avril 2002 03:41 -0400 [EMAIL PROTECTED] wrote:
> Hello,
>
>
>> well, I have a server with a database over 7GB, and :
>>
>> backup=> select count(*) from file;
>> count
>> --
>> 19430605
>> (1 row)
>>
>> backup=> explain analyze select * from file where id_file = 29
Hello,
> well, I have a server with a database over 7GB, and :
>
> backup=> select count(*) from file;
> count
> --
> 19430605
> (1 row)
>
> backup=> explain analyze select * from file where id_file = 2900;
> NOTICE: QUERY PLAN:
>
> Index Scan using file_pkey on file (cost=0.00.
24 matches
Mail list logo
