Re: [GENERAL] optimum postgres server configuration
* Disk speed 4 drives... 7200 RPM... as big as you can get. Get 8 Meg cache drives so you have a 3 year warranty. * Hardware RAID 3Ware IDE controller (or SATA) running RAID 10 * Memory 2 gig * Processor speed 1800+ * Processor type Athlon MP * Multiple processors 2 We are able to run a 60 person insurance company entirely off of the box I described above with ZERO load problems. And does the list have any observations regarding Postgres performance on different platforms? Our webservers run Linux (RedHat 8), but we're willing to experiment with alternatives. Many thanks Tom -+ tom dyson t: +44 (0)1608 811870 m: +44 (0)7958 752657 http://torchbox.com ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] Hardware Performance Tuning
I need to update that. 7.4 will use many more shared buffers by default. Yes, they are very small because we want to start even on small machines. --- Knut P. Lehre wrote: > The doc "PostgreSQL Hardware Performance Tuning" by Bruce Momjian, 16th > January 2003 says: "As a start for tuning, use 25% of RAM for cache size, > and 2-4% for sort size.", and "The default POSTGRESQL conguration allocates > 64 shared buffers. Each buffer is 8 kilobytes.". > Have I understood it correctly that "shared_buffers" should be set to 25% > of RAM divided by 8kB, and "sort_mem" to 2-4% of RAM? (If so, the default > values of 64 and 512 respectively, appear relatively small). > > Thanks, KP > > > > ---(end of broadcast)--- > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] plPHP -- sort of an announcement.. but not commercial
Tom Lane writes: > (Including PLs in the standard distro strikes me as a good idea, BTW. > They usually need maintenance along with the core backend code.) We could also say that keeping some PLs outside the core would keep us more honest in keeping the interfaces stable. The only maintenance that PLs really need to get are global search-and-replace bug fixes and making use of new server features. Consider, we already have (at least) Ruby, Sh, R, and Java language handlers out there, and we're not putting all of these in the core anytime soon. The handlers we currently have in the core cover the most popular languages, but there should be room for serious external development. Btw., one concern I have about putting this PHP thing in the core is that it would create a circular build dependency between PostgreSQL and PHP. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[GENERAL] v7.4 Beta 1 Bundle Available for Testing ...
Just a quick note to everyone that v7.4 is now official in Beta Freeze, with the first Bundle available for download, testing and bug reports ... The Bundle is available on all FTP mirrors (in both .gz and .bz2 format) under: /pub/source/v7.4 We encourage everyone that is able to download, test and report any bugs on this release to do so, so that we can ensure that this release is as strong as all our past releases. All bug reports should be addressed to: [EMAIL PROTECTED] Thank you Marc G. Fournier Co-ordinator PostgreSQL Global Development Group ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] Fatal error: Call to undefined function: pg_connect()
On Tuesday 05 August 2003 03:31 am, Jean-Christian Imbeault wrote: > shreedhar wrote: > > Is it necessary to uninstall previous version of PHP in my system. > > No，but a new recompile will probably over-write the version you have now. > > > Which is the better compatible version for Postgre 7.3.2. > > Most recent should be the best I would think. > > > Can you give any link/info for recompiling PHP > > www.php.net ? > > If you have never compiled PHP before I would suggest reading up on > compilation before-hand and even asking the php help list. Recompiling > PHP also means you need to recompile Apache (if that is the web server > you are using). No, you don't need to recompile Apache to recompile PHP, just restart the webserver. My guess would be when you update the new postgresql library override the old one, so PHP needs to be recompile to use the new library. My suggestion, easiest thing to do would be to write a PHP script with just and run the script (or browse it through the web). You will see all your old configure options there. Use that to configure your new PHP (make sure you have the option --with-pgsql), do "make", 'make install', and you should be good to go. RDB Reuben D. Budiardja Department of Physics and Astronomy The University of Tennessee, Knoxville, TN - /"\ ASCII Ribbon Campaign against HTML \ / email and proprietary format X attachments. / \ - Have you been used by Microsoft today? Choose your life. Choose freedom. Choose LINUX. - ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] multiple insert into's (may be NEWBIE question)
I have a table (lets say a,text b,text) and I want to insert the data jim,jimmy and trav,travis can I do this with 1 insert into statement instead of 2? Travis ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [GENERAL] plPHP -- sort of an announcement.. but not commercial
On Tue, 5 Aug 2003, Peter Eisentraut wrote: > Tom Lane writes: > > > (Including PLs in the standard distro strikes me as a good idea, BTW. > > They usually need maintenance along with the core backend code.) > > We could also say that keeping some PLs outside the core would keep us > more honest in keeping the interfaces stable. The only maintenance that > PLs really need to get are global search-and-replace bug fixes and making > use of new server features. > > Consider, we already have (at least) Ruby, Sh, R, and Java language > handlers out there, and we're not putting all of these in the core anytime > soon. The handlers we currently have in the core cover the most popular > languages, but there should be room for serious external development. > > Btw., one concern I have about putting this PHP thing in the core is that > it would create a circular build dependency between PostgreSQL and PHP. Agreed. I still want to know if we can have "safe mode" enabled and make a trusted / untrusted version. Is that workable? I would very much like to have a trusted version. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] Dump Customizing
A nice addition to the dump commands would be something like: -scope( schema( schema_s), tables( table_1), dbases_name objects( tables, indexes, constraints, types, functions, triggers, data, etc) ) if it could be completely hierarchial, then any set of objects desired could be extracted. Stephan Szabo wrote: On Tue, 5 Aug 2003, Yudha Setiawan wrote: Dear expert, It's Urgent. How do I dump just for - Table Structure - Index - Constraint - Type - Function. Without - Create Trigger. - Data. i've tried with -X option, but it didn't works "pg_dump -Upostgres test_yudha1 -fyudha1 -v -s -R -X disable-triggers;" Thank's for your attention. I don't think there is one that'll drop the create trigger statements so you'll probably need to do some post-processing on a schema only dump to get it. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[GENERAL] indices and cidr/inet type
in looking over the section of the users manual on indices, i see that
R-Tree indices are recommended for <<, but this advice is clearly tied to
the geometric interpretation of << ("to the left of") rather than the
network interpretation ("is contained in").
what type of index is recommended when the dominant lookup on a field is
'' << ipblock
where the ipblock column is of type cidr?
thanks,
richard
--
Richard Welty [EMAIL PROTECTED]
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Monthly table partitioning for fast purges?
I second that. I have discussed adding partitioning tables almost a year ago... No need to partition a functional index or anything like that. Just partition on a specific field. Ron Johnson wrote: >[...] > Partitioning "should" be put on the TODO list soon after tablespaces > (or DBA-defined directories) is implemented. > > -- > +-+ > | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | > | Jefferson, LA USA | > | | > | "I'm not a vegetarian because I love animals, I'm a vegetarian | > | because I hate vegetables!"| > |unknown | > +-+ > > ---(end of broadcast)--- > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[GENERAL] # Re: Monthly table partitioning for fast purges?
Below is the EXPLAIN ANALYZE output of a typical current query.
I have just begun looking at tsearch2 to index the header and body
fields.
I have also been using 'atop' to see I/O stats on the disk, i am now
pretty sure thats where the current bottleneck is. As soon as a query
is launched the IO goes up to 100% on sdh while the CPU sits at <40%.
EXPLAIN ANALYZE SELECT meta.msg_id, meta.date, meta.subject FROM
message, meta WHERE meta.date >= '2002-07-05 00:00:00' AND meta.date <=
'2002-08-05 00:00:00' AND message.body||message.header ILIKE '%chicken%'
AND meta.sys_id = message.sys_id ORDER BY col_date DESC;
QUERY PLAN
---
Nested Loop (cost=0.00..320901.89 rows=440 width=150) (actual time=
1558.44..344597.66 rows=2512 loops=1)
-> Index Scan Backward using meta_col_date_index on meta (cost=0.00..
54163.01 rows=88004 width=142) (actual time=29.17..46317.81 rows=149520
loops=1)
Index Cond: ((date >= '2002-07-05 00:00:00'::timestamp without time
zone) AND (date <= '2002-08-05 00:00:00'::timestamp without time zone))
-> Index Scan using nntp_message_pkey on nntp_message (cost=0.00..3.
02 rows=1 width=8) (actual time=1.99..1.99 rows=0 loops=149520)
Index Cond: ("outer".sys_id = message.sys_id)
Filter: ((body || header) ~~* '%chicken%'::text)
Total runtime: 344612.85 msec
(7 rows)
Thanks!
--
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Fatal error: Call to undefined function: pg_connect()
Hi did you configure php for PostgreSQL support ./configure --with-pgsql Regards Conni ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
