Minor documentation bug

Joseph Shraibman <jks@selectacast.net> writes:

In /usr/local/pgsql/doc/html/runtime-config.html:
The order of the lists do not seem to match.

Definitely a tad confused --- fixed for 7.1.1.

BTW can I send to the bugs list w/o subscribing?

The current policy on the pg lists is you can post anyplace, but your
post will be delayed for human approval if you're not subscribed.
(Typically it'll take a day or so for Marc to get around to it...)
AFAIK pgsql-bugs is not different from the rest.

I believe there's a form somewhere on our website that you can fill out
to send to pgsql-bugs without being subscribed, also. I don't think
those submissions are delayed (we haven't been spammed via the form
yet ;-)).

regards, tom lane

The current policy on the pg lists is you can post anyplace, but your
post will be delayed for human approval if you're not subscribed.
(Typically it'll take a day or so for Marc to get around to it...)
AFAIK pgsql-bugs is not different from the rest.

I believe there's a form somewhere on our website that you can fill out
to send to pgsql-bugs without being subscribed, also. I don't think
those submissions are delayed (we haven't been spammed via the form
yet ;-)).

Isn't that the loopback address?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

On Mon, 30 Apr 2001, Tom Lane wrote:

Joseph Shraibman <jks@selectacast.net> writes:

In /usr/local/pgsql/doc/html/runtime-config.html:
The order of the lists do not seem to match.

Definitely a tad confused --- fixed for 7.1.1.

BTW can I send to the bugs list w/o subscribing?

The current policy on the pg lists is you can post anyplace, but your
post will be delayed for human approval if you're not subscribed.
(Typically it'll take a day or so for Marc to get around to it...)
AFAIK pgsql-bugs is not different from the rest.

I believe there's a form somewhere on our website that you can fill out
to send to pgsql-bugs without being subscribed, also. I don't think
those submissions are delayed (we haven't been spammed via the form
yet ;-)).

There's a link to the BugTool on the PostgreSQL home page and there's
no delay in the report getting posted to the bug list.

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================

Hello all,

I have tried several times to make postgresql with ssl support, all times
i got the following error:

In file included from crypt.c:27:
/usr/include/crypt.h:23: conflicting types for `des_encrypt'
/usr/local/ssl/include/openssl/des.h:144: previous declaration of
`des_encrypt'

crypt.h defines it as : extern void des_encrypt(char *, int);

des.h defines it as : /usr/local/ssl/include/openssl/des.h;

this is definitely a conflict. any suggestions?

thanks in advance,
--chris

Hello all,

In continuing my quest from yesterday to speed up some INSERTs I'm doing, I
came across a SELECT statement in my trigger that is taking .433 seconds to
run. Here is a sample query:

select * from status s where s.site_id = 18 and s.host_id = 49 and
s.product = 'BETA' and s.class = 'APPS' and s.subclass = 'MONITOR' ;

I had drastically increased performance of some other queries this morning
by adding a multicolumn index on the table, so I thought I would try here
as well. Here's the table and the index I created:

Table "status"
Attribute | Type | Modifier
-----------+-----------+----------
site_id | bigint | not null
host_id | bigint | not null
product | varchar() | not null
class | varchar() | not null
subclass | varchar() | not null
status | varchar() | not null
msg | varchar() |
tstamp | timestamp |
Indices: status_5_column_index,
status_host_id_key,
status_site_id_key

The query I used to create the index: create index status_5_column_index
on status (site_id, host_id, product, class, subclass);

I then ran some tests. It's still taking .433 seconds on average. Is a 5
column multicolumn index too much for postgres to handle? Is my query not
using the index at all? Is my database designed horrendously and the mere
fact that I have a select with 5 where conditions making you ill? :-) It
worked for two columns this morning, so I thought I'd give this a shot.

Thanks,
Fran

Our db server running 7.1 got *torched* today, system ran between 30% an
80% CPU all day! Right now the server is running on a Penguin Computing
800mhz PIII w/ 128 ram and IDE hardware.

Tomorrow I'd like to place an order for something more robust... looking
into dual PIII, gig of ram and SCSI Raid. Planning on running Red Hat 7.1
on this machine.

Before I order, I was wondering if anyone had any suggestions or
recommendations. I have been considering getting a Sun machine... but I
don't know if there is a benefit. Also, are there any special
considerations when running RAID and dual CPU?

You're input is tremendously appreciated!

-r

Ryan Mahoney
CTO, Payment Alliance, Inc.
ryan@paymentalliance.net
t. 718-721-0338
m. 718-490-5464
www.paymentalliance.net

Fran Fabrizio <ffabrizio@exchange.webmd.net> writes:

I then ran some tests. It's still taking .433 seconds on average. Is a 5
column multicolumn index too much for postgres to handle?

No, but without some EXPLAIN output (maybe even EXPLAIN VERBOSE output)
it's quite impossible for anyone to guess what may be happening here.

regards, tom lane

Hi Chris,

This is a known problem with some versions of OpenSSL.

Details of a workaround can be found at :

http://techdocs.postgresql.org/bugsfixes.html#solaris

Regards and best wishes,

Justin Clift

Chris Hayner wrote:

Hello all,

I have tried several times to make postgresql with ssl support, all times
i got the following error:

In file included from crypt.c:27:
/usr/include/crypt.h:23: conflicting types for `des_encrypt'
/usr/local/ssl/include/openssl/des.h:144: previous declaration of
`des_encrypt'

crypt.h defines it as : extern void des_encrypt(char *, int);

des.h defines it as : /usr/local/ssl/include/openssl/des.h;

this is definitely a conflict. any suggestions?

thanks in advance,
--chris

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi

I checked and this has been corrected.

In /usr/local/pgsql/doc/html/runtime-config.html:

DEBUG_PRINT_PARSE (boolean), DEBUG_PRINT_PLAN (boolean),
DEBUG_PRINT_REWRITTEN (boolean), DEBUG_PRINT_QUERY
(boolean),DEBUG_PRETTY_PRINT (boolean)

For any executed query, prints either the query, the parse tree,
the execution plan, or the query rewriter output to the server log.
DEBUG_PRETTY_PRINT selects
are nicer but longer output format.

The order of the lists do not seem to match.

BTW can I send to the bugs list w/o subscribing? I'm not sure so I'm
sending to general.

--
Joseph Shraibman
jks@selectacast.net
Increase signal to noise ratio. http://www.targabot.com

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026