Thomas F. O'Connell wrote:
Joshua,
Is there any difference between a catalog and a cluster? As in, are you
saying a separate postmaster per user, as Tom Lane suggested in the
post I referenced earlier in this thread?
No difference. Yes as Tom Lane suggested. It also helps with migration.
If a customer moves servers (or upgrades to dedicated etc..) you just
stop the database, move it (as long as it is the same arch) and start it
back up :)
Off-hand, do you (or anyone else) see any showstoppers with the
implementation I laid out involving a bit of mucking with system
catalogs and the schema search path?
I honestly didn't read through the whole thing. It looked like a whole
bunch of administrative trouble to me ;)
Sincerely,
Joshua D. Drake
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On Jul 11, 2005, at 12:01 PM, Joshua D. Drake wrote:
Although it is resource intensive, Command Prompt creates a new catalog
owned by the user for each account. So on a given machine we will have
25 postgresql catalogs running on separate ports.
This has worked very well for us for the last couple of years.
Sincerely,
Joshua D. Drake
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
