Re: [HACKERS] Rigth toolset to compile under mingw?
I have tried to compile 8.1.3 with mingw but I am receiving come errors, I do not know with versions are the correct one. Could some body tell me the right versions ? and url's to download from ? please. I searched the mainling lists but it is not clear. Magnus Hagander has pointed me to http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/README?re v=1.18content-type=text/x-cvsweb-markup Which contains useful information. I will help you if I can, send me an e-mail with details of your problems. Yours, Laurenz Albe ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] Explaining Explain
I'm looking for some comphrensive article explaining the Optimizer, i.e detailed explanation on Hash joins, Nested Joins etc., and why would the Optimizer choose that. can anybody point me to some good tutorials and resources? regards, Luckys
[HACKERS] Support Parallel Query Execution in Executor
I have written some experimental code of doing master-slave seqscan in
PostgreSQL. During the work, I feel we had enough infrastructure to support
parallel query execution.
What I did is adding a new node PARA and plug it above the node that we want
to execute in parallel. In this stage, a PARA node is just a SeqScan node,
which is:
typedef struct Para
{
/* TODO: add a union to put all nodes supporting parallism here */
SeqScan scan;
/* Split / Merge / Redistribute */
ParaTypetype;
/* TODO: other possible parameters */
} Para;
At the execution, the master (the process who receives the query) will wake
up a slave process (an idle ordinary backend) and the slave will pass the
scan results to the master via a shared memory communication-buffer. In
details, the execution is like this:
Master process:
1. PARA init: wake up a slave, pass the queryTree and outerPlan(planTree) to
it by nodeToString();
2. PARA exec:
get an item from the communication-buffer;
if item is a valid tuple
return item;
else
handle other types of item;/* execution done/error */
3. PARA end: do some cleanup.
As we can see from PARA init stage, with even the most simple PARA node, it
is easy to support inter-node parallism.
Slave process (use similar code for autovacuum process):
1. Get queryTree and planTree;
2. Redirect the destReceiver to the communication-buffer;
3. Encapsulate them in an executor and run;
The query plan is like this:
TEST=# explain select max(a), max(b) from t;
QUERY PLAN
--
Aggregate (cost=7269.01..7269.02 rows=1 width=53)
- Para [Split = 1] (cost=10.00..5879.00 rows=278000 width=53)
- Seq Scan on T (cost=0.00..5879.00 rows=278000 width=53)
(3 rows)
There are some problems I haven't addressed yet. The most difficult one for
me is the xid assignment: master and slaves should see an identical view,
and the key is the xid. I am not sure the correct solution of this problem.
We may use the same xid or use a continuous portion of xids for master and
slaves. There are other problems like the login problem (the master and
slaves should be acting as the same user), the elog message passing etc are
also important but I think we are able to handle them without any problem.
I haven't touched the most difficult part, the parallel query optimizer. But
thanks to the two-phase parallel optimization technique, this part can be
treated as the geqo optimizer, without enough evidence, we don't enable
parallel query execution.
Is there any show-stop reasons of not doing this?
Regards,
Qingqing
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Re: [HACKERS] Support Parallel Query Execution in Executor
On Thu, Apr 06, 2006 at 06:28:33PM +0800, Qingqing Zhou wrote: I have written some experimental code of doing master-slave seqscan in PostgreSQL. During the work, I feel we had enough infrastructure to support parallel query execution. Good work. One question though, temporary tables. Currently there no way to get a consistant view of a temporary table from another process. You probably have to avoid shipping off non-immutable function calls. Is it possible to deadlock (don't see how, but I may not be looking hard enough). Hardest work would be finding what can be safely farmed off. Nice work though, I hadn't thought of this approach. Have a nice day, -- Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/ Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. signature.asc Description: Digital signature
Re: [HACKERS] Summer of Code Preparation
On Wed, Apr 05, 2006 at 11:55:15PM -0300, Marc G. Fournier wrote: On Wed, 5 Apr 2006, Jim Nasby wrote: One idea that comes to mind is to come up with a list of popular OSS projects that we'd like to see add PostgreSQL support and have students work on those... As nice an idea as this is, we'd also need to quickly co-ordinate with those projects to make sure that there is a semblance of a chance of having those patches included in their distribution ... I realize that the Code of Summer program doesn't need a guarantee that the code will be committed, but if we're going to do something like the above, would rather see it done for projects that wanted the end results ... Absolutely, though we can't do that without a list of possibilities first. People want to start throwing out names? (I can't really think of any off the top of my head, other than OpenQRM, but I have ulterior motives for that one so perhaps my vote shouldn't count. :) ) -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Explaining Explain
2006/4/6, Luckys [EMAIL PROTECTED]: I'm looking for some comphrensive article explaining the Optimizer, i.e detailed explanation on Hash joins, Nested Joins etc., and why would the Optimizer choose that. can anybody point me to some good tutorials and resources? A Tour of PostgreSQL Internals: url:http://www.postgresql.org/files/developer/tour.pdf Recent PostgreSQL Optimizer Improvements: url:http://conferences.oreillynet.com/cs/os2003/view/e_sess/4372 Inside the PostgreSQL Query Optimizer: url:http://lca2005.linux.org.au/Papers/Neil%20Conway/Inside%20the%20PostgreSQL%20Query%20Optimizer/index.html The manual: url:http://www.postgresql.org/docs/current/static/planner-optimizer.html Nicolas -- Nicolas Barbier http://www.gnu.org/philosophy/no-word-attachments.html ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Support Parallel Query Execution in Executor
On 4/6/06, Qingqing Zhou [EMAIL PROTECTED] wrote: I have written some experimental code of doing master-slave seqscan in PostgreSQL. During the work, I feel we had enough infrastructure to support parallel query execution. Great work! I had looked into this a little bit and came to the same ideas/problems you did, but none of them seemed insurmountable at all. I'd be interested in working with you on this if you'd like. I'm interested in hearing Tom's suggestions on this topic too. -- Jonah H. Harris, Database Internals Architect EnterpriseDB Corporation 732.331.1324 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] Strange results from to_timestamp
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
---
0001-01-01 03:00:00+01 BC
(1 row)
Questionable, but probably valid.
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
0300-12-25 03:00:00+01
(1 row)
This puzzles me. Where is the 25th of december coming from?
mydb=# select to_timestamp(' 030004','mmdd hh24mi');
to_timestamp
0382-04-23 03:00:00+01
(1 row)
Same as above.
mydb=# select to_timestamp(' 040004','mmdd hh24mi');
to_timestamp
0509-10-10 04:00:00+01
I think all except the first one should raise a warning, isn't it? Where can I
find the source code of this function?
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Re: [HACKERS] Strange results from to_timestamp
Am Donnerstag, 6. April 2006 14:57 schrieb Mario Weilguni:
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
---
0001-01-01 03:00:00+01 BC
(1 row)
Questionable, but probably valid.
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
0300-12-25 03:00:00+01
(1 row)
This puzzles me. Where is the 25th of december coming from?
Sorry, forgot to mention, this is from PostgreSQL 8.1.3
---(end of broadcast)---
TIP 6: explain analyze is your friend
Re: [HACKERS] Explaining Explain
On Thursday 06 April 2006 07:43, Nicolas Barbier wrote:
2006/4/6, Luckys [EMAIL PROTECTED]:
I'm looking for some comphrensive article explaining the Optimizer, i.e
detailed explanation on Hash joins, Nested Joins etc., and why would the
Optimizer choose that.
can anybody point me to some good tutorials and resources?
A Tour of PostgreSQL Internals:
url:http://www.postgresql.org/files/developer/tour.pdf
Recent PostgreSQL Optimizer Improvements:
url:http://conferences.oreillynet.com/cs/os2003/view/e_sess/4372
Inside the PostgreSQL Query Optimizer:
url:http://lca2005.linux.org.au/Papers/Neil%20Conway/Inside%20the%20Postgr
eSQL%20Query%20Optimizer/index.html
The manual:
url:http://www.postgresql.org/docs/current/static/planner-optimizer.html
I feel somewhat obligated to add the following to the list:
http://techdocs.postgresql.org/oscon2005/robert.treat/ contains the open
office presenation file. If you google on explaining explain you can get
an html version.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
[HACKERS] About pg_hba.conf
Hello Folks, This may be a dumb question but please bear a moment with me. About the TODO item %Allow pg_hba.conf settings to be controlled via SQL: If in the future we could configure the settings by SQL commands, assuming the settings are saved in an internal table, what would be the need for a pg_hba.conf file anymore. (except for the backward compatibility of cource) Regards, Gevik ---(end of broadcast)--- TIP 1: 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
[HACKERS] Windows installer bugs (was: [BUGS] BUG #2374: Installation Error)
-bugs is getting inundated with windows installer bugs, and people on the list don't seem to be replying to them. Can someone with the installer project add more prominent information about where users should be reporting installer bugs to? (I'm guessing that the installer has a bug tracker, but I'm not online right now to check...) Begin forwarded message: From: Rick Craft [EMAIL PROTECTED] Date: April 4, 2006 4:26:33 AM EDT To: pgsql-bugs@postgresql.org Subject: [BUGS] BUG #2374: Installation Error The following bug has been logged online: Bug reference: 2374 Logged by: Rick Craft Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: Windows XP Professional Description:Installation Error Details: Whenever I select a Service Username, I get a message that localhost\username does not exist, do I want to create an account. When answering YES, a password is automatically generated, and the installation continues. After installing all of the DLL's and modules, it says that the username that I created at the beginning already exists and then it does a rollback. this happens no matter what username I try to create as the Service username. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 1: 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: [HACKERS] domain_in performance considerations
Tom Lane wrote: Hi, It would be just a small change to make the code cache the EState across calls, saving a link to it in the FmgrInfo, but I am worried about that. If the EState's query context is made to be a child of the memory context containing the caller's FmgrInfo, then there is no problem as far as memory management goes --- destroying that parent context will make all the memory associated with the EState go away. The problem is that an EState might have other open resources, principally buffer pins, and there would not be any clean way to close down those resources when the EState is no longer needed. We don't have any sort of shutdown callback that domain_in could make use of in the general case. This is a shot in the dark, but I remember you commenting awhile back that there was a way to register a callback to be called on memory context reset or delete. I wonder if it would be possible to create a separate ResourceOwner for the EState, and save the EState in a certain memory context so that a callback would release the buffer pins or whatever. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Windows installer bugs (was: [BUGS] BUG #2374: Installation Error)
It does, and it's listed on the page. It clearly states use the mailinglists for general stuff, and the trackers for installer specific issues. However, this is the official installer for pg on win32. And I'd expect a lot of new users not to know (or understand) the distinction that the installer is not a part of the database project. To people from the outside, that just doesn't make sense. Don't expect ppl to actually *read* what's on the pages. ;-) For example, it clearly says don't download from here, download from the ftp network, and we still get an avg of some 400 downloads per day, with well over 1000/day around releases. (That just download a HTML file with a redirect to the ftp network, so pgFoundry stands a chance of surviving) (Notice that we also have text saying please don't post postgresql bugs here, just installer bugs, and we still regularly get bug reports about general backend stuff) Now, it would certainly help if more people could actually help in *answering* the bugs/questions that are posted :), but that's a different question... //Magnus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Nasby Sent: Thursday, April 06, 2006 1:42 PM To: pgsql-hackers@postgresql.org Subject: [HACKERS] Windows installer bugs (was: [BUGS] BUG #2374: Installation Error) -bugs is getting inundated with windows installer bugs, and people on the list don't seem to be replying to them. Can someone with the installer project add more prominent information about where users should be reporting installer bugs to? (I'm guessing that the installer has a bug tracker, but I'm not online right now to check...) Begin forwarded message: From: Rick Craft [EMAIL PROTECTED] Date: April 4, 2006 4:26:33 AM EDT To: pgsql-bugs@postgresql.org Subject: [BUGS] BUG #2374: Installation Error The following bug has been logged online: Bug reference: 2374 Logged by: Rick Craft Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: Windows XP Professional Description:Installation Error Details: Whenever I select a Service Username, I get a message that localhost\username does not exist, do I want to create an account. When answering YES, a password is automatically generated, and the installation continues. After installing all of the DLL's and modules, it says that the username that I created at the beginning already exists and then it does a rollback. this happens no matter what username I try to create as the Service username. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 1: 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 ---(end of broadcast)--- TIP 1: 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: [HACKERS] domain_in performance considerations
Alvaro Herrera [EMAIL PROTECTED] writes: This is a shot in the dark, but I remember you commenting awhile back that there was a way to register a callback to be called on memory context reset or delete. AFAIR there's no such thing associated with memory contexts per se. There is one for EStates, but that requires access to an outer EState, which is exactly what we lack for the other solution too. I wonder though if we shouldn't invent one for memory contexts. Maybe even replace the EState-specific shutdown callback with mcontext cleanup on its query context? regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Windows installer bugs (was: [BUGS] BUG #2374: Installation
Magnus Hagander wrote: Now, it would certainly help if more people could actually help in *answering* the bugs/questions that are posted :), but that's a different question... //Magnus I have created a very nice installer using Inno setup and it is about 50 times easier to code for than the current cryptic WIX setup. Why don't you have a look? Here is the source with a bsd license: http://www.amsoftwaredesign.com/downloads/pg_installer_setup.zip All the create user and runas stuff is done using API commands via a Delphi or Free Pascal DLL(not tested but should work) It does not use the RunAs service at all and handles the initDB. You could also use a C or C++ dll just as easily. Just reminding everyone it's out there. -- Tony Caduto AM Software Design http://www.amsoftwaredesign.com Home of PG Lightning Admin for Postgresql Your best bet for Postgresql Administration ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] About pg_hba.conf
Gevik Babakhani wrote: This may be a dumb question but please bear a moment with me. About the TODO item “%Allow pg_hba.conf settings to be controlled via SQL“: If in the future we could configure the settings by SQL commands, assuming the settings are saved in an internal table, what would be the need for a pg_hba.conf file anymore. (except for the backward compatibility of cource) System recovery might also be a reason (if you for some reason make your data in DB unworkable). Svenne smime.p7s Description: S/MIME Cryptographic Signature
Re: [HACKERS] About pg_hba.conf
Gevik Babakhani schrieb: Hello Folks, This may be a dumb question but please bear a moment with me. About the TODO item “%Allow pg_hba.conf settings to be controlled via SQL“: If in the future we could configure the settings by SQL commands, assuming the settings are saved in an internal table, what would be the need for a pg_hba.conf file anymore. (except for the backward compatibility of cource) No, you need the ability to override the settings with external options to get access to a misconfigured database. (Well of course you could run postgres in single user mode to get that too, but it would be a little inconvient...) Regards Tino ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Support Parallel Query Execution in Executor
Jonah H. Harris wrote: On 4/6/06, Qingqing Zhou [EMAIL PROTECTED] wrote: I have written some experimental code of doing master-slave seqscan in PostgreSQL. During the work, I feel we had enough infrastructure to support parallel query execution. Great work! I had looked into this a little bit and came to the same ideas/problems you did, but none of them seemed insurmountable at all. I'd be interested in working with you on this if you'd like. I'm interested in hearing Tom's suggestions on this topic too. From time to time there is (often ill-informed) discussion about making postgres multi-threaded - this strikes me as a possible candidate area for multithreading, and maybe that would be a way to overcome some of the problems mentioned. Just a thought cheers andrew ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] About pg_hba.conf
On Thursday 06 April 2006 09:45, Gevik Babakhani wrote:
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table, what would be the
need for a pg_hba.conf file anymore. (except for the backward
compatibility of cource)
I've generally been keeping the idea around as a foot-gun saver for when
people lock themselves out of the database via the sql commands; this could
give them a fall back mechanism to do authentication without something more
drastic.
I think some people might also prefer the pg_hba.conf method as more secure,
since it requires local access to modify, making remote exploits a wee bit
harder (admin tools that provide this functionality not-withstanding)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: [HACKERS] About pg_hba.conf
I agree. Security is a good reason to have the pg_bha.conf around. I guess
it would make the TODO item a bit harder to develop hence one has to read
and write the file to support the future SQL commands too. I also looked
at the code for a moment; perhaps using a yacc/lex mechanism would make
things easier to develop the TODO item. Like creating a simple parser for
the config file to be able to read and or update it.
Reagrds,
Gevik.
On Thursday 06 April 2006 09:45, Gevik Babakhani wrote:
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table, what would be the
need for a pg_hba.conf file anymore. (except for the backward
compatibility of cource)
I've generally been keeping the idea around as a foot-gun saver for when
people lock themselves out of the database via the sql commands; this
could
give them a fall back mechanism to do authentication without something
more
drastic.
I think some people might also prefer the pg_hba.conf method as more
secure,
since it requires local access to modify, making remote exploits a wee bit
harder (admin tools that provide this functionality not-withstanding)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
Re: [HACKERS] About pg_hba.conf
[EMAIL PROTECTED] (Gevik Babakhani) writes: This may be a dumb question but please bear a moment with me. About the TODO item %Allow pg_hba.conf settings to be controlled via SQL: If in the future we could configure the settings by SQL commands, assuming the settings are saved in an internal table, what would be the need for a pg_hba.conf file anymore. (except for the backward compatibility of cource) It's a frequently asked question... The trouble is, what if you accidentally lock all of the users out? How do you fix that, if nobody can connect to submit SQL commands? -- (reverse (concatenate 'string moc.enworbbc @ enworbbc)) http://www.ntlug.org/~cbbrowne/lsf.html Ahhh. A man with a sharp wit. Someone ought to take it away from him before he cuts himself. -- Peter da Silva ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[HACKERS] pgadmin III's Chinese simplified translations
i have continued the pgadmin III's Chinese simplified translations,hope this translate will release with the next version of pgadmin III.thanks. how can i submit this translate-- 我渴望平静，风却给了我涟漪
Re: [HACKERS] Support Parallel Query Execution in Executor
Jonah H. Harris [EMAIL PROTECTED] wrote Great work! I had looked into this a little bit and came to the same ideas/problems you did, but none of them seemed insurmountable at all. I'd be interested in working with you on this if you'd like. Yes, I am happy to work with anyone on the topic. The plan in mind is like this: (1) stable the master-slave seqscan: solve all the problems left; (2) parallize the seqscan: AFAICS, this should not very difficult based on 1, may only need some scan portition assignment; (3) add an indexscan or other one or two node type to master-slave solution: this is in order to make the framework extensible; (4) parallize these node - this will be a big chunk of job; (5) add a two-phase optimization to the server - we have to consider the partitioned table in this stage, yet another big chunk of job; Regards, Qingqing ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] commit callback, request, SOLVED
=?ISO-8859-2?Q?Horv=E1th_S=E1ndor?= [EMAIL PROTECTED] writes: In the documentation: CREATE CONSTRAINT TRIGGER is used within CREATE TABLE/ALTER TABLE and by pg_dump to create the special triggers for referential integrity. It is not intended for general use. What means it is not intended for generally use? What it really means is that we don't promise to keep this compatible in the future. There will probably always be something similar, but you might have to change your application to use it. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Strange results from to_timestamp
Mario Weilguni [EMAIL PROTECTED] writes: I think all except the first one should raise a warning, isn't it? to_timestamp (and friends) all seem to me to act pretty bizarre when faced with input that doesn't match the given format string. However, in the end that is an Oracle-compatibility function, and there is only one measure of what it should do: what does Oracle do in the same case. Can anyone try these examples on a recent Oracle version? regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Windows installer bugs (was: [BUGS] BUG #2374: Installation Error)
On Thu, Apr 06, 2006 at 03:55:20PM +0200, Magnus Hagander wrote: Now, it would certainly help if more people could actually help in *answering* the bugs/questions that are posted :), but that's a different question... Well, that's my primary concern. It seems that people aren't replying to bugs posted -bugs about the windows installer. I just want to make sure they're being addressed. All the ones I saw seemed to come in from the web form, so we should probably put something on that page as well. Or better yet, set it up so that for select projects such as the installer people can report bugs using the main bug form and they'll end up in the appropriate tracker on pgFoundry. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
