[ADMIN] ERROR: Conditional NOTIFY is not implemented

2001-08-21 Thread matthew . copeland
I have a set of rules that worked in 7.0.3 for async notification. Those same set of rules don't seem to be working under 7.1.2. The rules look like this. CREATE RULE CONFIG_CHNG AS ON INSERT TO gs_config DO (NOTIFY CONFIG_CHANGE); CREATE RULE CONFIG_CHNG AS ON UPDATE TO gs_config DO (NOTIFY C

Re: [ADMIN] ever growing pkey files

2001-08-15 Thread matthew . copeland
Well, I reindexed on 7.0.3, and that worked. I also upgraded, and that worked with my code also, so ignore the not working comment. Thanks for the help, Matthew M. Copeland On Tue, 14 Aug 2001 [EMAIL PROTECTED] wrote: > > Yeah, VACUUM doesn't shrink indexes presently (it's on the TODO > >

Re: [ADMIN] ever growing pkey files

2001-08-14 Thread matthew . copeland
> Yeah, VACUUM doesn't shrink indexes presently (it's on the TODO > list...). > > > PostgreSQL version 7.0.3 running under Linux. > > You could try REINDEX to rebuild the indexes, but I'd recommend updating > to 7.1.2 (or soon, 7.1.3) first. I don't recall whether REINDEX is > available/trustwo

[ADMIN] ever growing pkey files

2001-08-14 Thread matthew . copeland
I have a database that has two tables. One of the tables gets changed very often. (like every 5 minutes). The values that where in the table are replaced with a new set of values with new unique keys. Now, I vacuum these tables fairly often, but the pkey files for these tables never seem to g

[ADMIN] problem creating database

2000-11-03 Thread matthew . copeland
I'm using postgresql 7.0.2 compiled from the source. I seem to have things up and working, but I am getting the problem shown below. I can psql into another database, if I use a different name, and on another system I can create a database with the name product. I even tried dropping it and re