DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=XI8mxPm2/7VnK7pRgAIJ1RMPXLBFrD6NvmjA3tBFojrcND7aAhJKP4a1kQfRXq9Dys
	lbGLxX3U4HrTwpM0JnSfiBJVppHyOY25347EEsppiJgkMAu9TiXJ/F4NW4MqeL77+Tz7
	aqq0KDxIyQFCeA/c1ZeBdLu9ZSN3F/4TVYXoA=
Message-ID: <dcc563d10810141721i4cb87bc7sb9ca1f6f33d64ecf@mail.gmail.com>
Date: Tue, 14 Oct 2008 18:21:06 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: Chris <dmagick@gmail.com>
Subject: Re: Drupal and PostgreSQL - performance issues?
Cc: pgsql-general@postgresql.org
In-Reply-To: <48F53626.3000404@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2434A118-CEFA-43A9-BA88-006EC1F80326@hoegh.org>
	<e7e0a2570810131945x1bbf10b8r67c0ac2a340b436f@mail.gmail.com>
	<20081014114011.0ebe495a@dawn.webthatworks.it>
	<dcc563d10810140556v399ce9ddq94e9c88da2b8a742@mail.gmail.com>
	<8c8854360810140647n58abc9bend377e0e234dd39a9@mail.gmail.com>
	<BLU142-W253E0943D6748CDC17421DAE310@phx.gbl>
	<8c8854360810140828p3b81bba0xac006f5565519981@mail.gmail.com>
	<48F51EB4.3090908@gmail.com>
	<dcc563d10810141700q6faed970q7b63a056b25d91f4@mail.gmail.com>
	<48F53626.3000404@gmail.com>

On Tue, Oct 14, 2008 at 6:15 PM, Chris <dmagick@gmail.com> wrote:
>
>> Are you saying you have to reconnect to change schemas?  In Oracle and
>> PostgreSQL both you can change the current schema (or schemas for
>> postgresql) with a single inline command.
>
> No I meant you have to change the schema after connecting.
>
> Some hosts only give you one db & one user. Yeh it sucks but that's all they
> give you.

Yeah, if you could at least have multiple users with pgsql it would be
ideal.  connect via user1, inherit his search_path, connect via user2,
inherit the default search path, etc...

> Before anyone says "get a new host".. from the end user POV.. you don't know
> and/or don't care about the technical details, you just want something "that
> works" with what you have. It's not an ideal situation to be in but it
> definitely does happen.

Understood.  We aren't all working on large corporate in house servers
for our stuff that we can configure how we want.

>>> Shared hosts don't give you a lot of resources, so apps build stuff like
>>> that in to make it easier.
>>
>> Schemas cost virtually nothing.
>
> Neither does building a smart(er) app which lets you set a "prefix" for all
> of your tables so they are grouped together.

True.  Given that MySQL treats the first of three identifiers in dot
notation as a db, and pg treats them as a schema, it would be a better
solution to have pg use schemas and mysql use dbs.  Except for the
hosting providers.

> You'll get a tiny performance hit from doing the replacement of the prefix,
> but it's not going to be significant compared to everything else.

Yeah, it's likely lost in the noise.  I'd be more worried about ugly queries.