Re: [GENERAL] WinXP + PgSQL 8 beta3 = impossible?

2004-09-30 Thread Campano, Troy
I was able to install PostgreSQL 8 Beta 2 with pgInstaller on Windows XP Professional without any problems. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BARTKO, Zoltán Sent: Thursday, September 30, 2004 5:54 AM To: [EMAIL PROTECTED] Subject: [GENERAL

[GENERAL] PostgreSQL Optimizer

2004-06-24 Thread Campano, Troy
Title: PostgreSQL Optimizer Hello, Is PostgreSQL’s optimizer cost based or syntactical based? Thank you!

[GENERAL] Prevent users from creating tables

2004-06-08 Thread Campano, Troy
Title: Prevent users from creating tables Hello, I’m trying to set up PostgreSQL for proof of concept according to our standards. I need to create a user for database01 that has the ability to create any objects they want. They can create tables, views, indexes, etc. Then I need a second

Re: [GENERAL] Backup and Restore of PostgreSQL

2004-06-07 Thread Campano, Troy
Easiest thing to do is to call pgsql from your servlet, have it dump the file somewhere in your web apps directory, and then either send the link to that file to the client or automatically forward the client there. Option 2 would be to use JDBC to view the meta data of the table and use it to wr

[GENERAL] statement-level statistics are disabled error (postgresql.conf)

2004-06-02 Thread Campano, Troy
Title: statement-level statistics are disabled error (postgresql.conf) Do you know what I did wrong? I’m trying to enable some logging features in postgresql.conf, but now I get this message when I try to connect to the postgresql server… WARNING:  statement-level statistics are disabled b

[GENERAL] Databases on separate filesystems

2004-06-01 Thread Campano, Troy
I need to have each one of my PostgreSQL databases put on a separate filesystem. I wanted to do the following…can someone verify that this will work?     1)   Create the following environment variables: a. export PGDATA01=/filesystem1 b. export PGDATA02=/filesystem2 c. export PGDATA

Re: [GENERAL] Database Size Limiting

2004-05-27 Thread Campano, Troy
3:23 PM To: Joshua D. Drake Cc: Campano, Troy; Postgres general mailing list Subject: Re: [GENERAL] Database Size Limiting Joshua D. Drake wrote: > Hello, > > You could use Filsystem quotas but I strongly suggest against it as it > will probably bring about database corruption.

Re: [GENERAL] Database Size Limiting

2004-05-27 Thread Campano, Troy
ke [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 2:12 PM To: Campano, Troy Cc: Postgres general mailing list Subject: Re: [GENERAL] Database Size Limiting Hello, You could use Filsystem quotas but I strongly suggest against it as it will probably bring about database corruption. A bette

[GENERAL] Database Size Limiting

2004-05-27 Thread Campano, Troy
Title: Database Size Limiting Is there a way to limit the size that an individual database can take up? My understanding is that all your databases go into a file system which is your ‘catalog cluster’. But all the databases can grow until that filesystem is full. Is there a way to limi

Re: [GENERAL] Timestamp problems...wrong weeks.

2004-04-29 Thread Campano, Troy
EMAIL PROTECTED] On Behalf Of Andrew Sullivan Sent: Thursday, April 29, 2004 3:42 PM To: Pgsql-General Subject: Re: [GENERAL] Timestamp problems...wrong weeks. On Thu, Apr 29, 2004 at 02:42:49PM -0400, Campano, Troy wrote: > > This is causing my reports to print out incorrect data. > D

[GENERAL] Timestamp problems...wrong weeks.

2004-04-29 Thread Campano, Troy
Title: Timestamp problems...wrong weeks. Hello, I’m having a problem with timestamps in postgresql. I run the following query to pull dates in this format: WEEK/MONTH/YEAR However the data says that April 28th 2004 was in week 4 of April and that April 29th 2004 was in week 5 of april.

[GENERAL] db_space

2004-02-09 Thread Campano, Troy
Title: db_space Is there a way to get the size of your PostgreSQL database using sql? I need this for an inventory program. Thanks! Troy Campano Liberty Mutual Infrastructure Software Engineering Database Management desk: (603) 245 4092 cell: (603) 219 5539 [EMAIL PROTECTED]