Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D84BC64FDE5 for ; Tue, 14 Oct 2008 21:00:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 68147-04 for ; Tue, 14 Oct 2008 21:00:25 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by postgresql.org (Postfix) with ESMTP id 3BA6C64FDDF for ; Tue, 14 Oct 2008 21:00:25 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id j4so1378696wah.19 for ; Tue, 14 Oct 2008 17:00:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=weNcQPIul0saWkLlT8ZPS59KQbXgrpSeCgJCCu+K2Nc=; b=w3fvNPDbBH0Nn/26pGJZghn0THcTigcIXCPhekVFhNwsw5FGBoP3aq3aQ35e0cAue0 utPkCsvEAa9/vEJ4RD92XQcohS894x6ggebbEUMfR2oRICW5dLDmEYndceeZybEAnJWy hlanKtTNElX+fW+j7vdS7ZPJRlzuAVS6ssjQs= 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=Hs/mKKFr1h97UrKyYPBrE5DqWxC4XOzgVTEKs22Nl/LiuT1VzFVsZyrSOQknQynM68 XLOmC068XYdyKitRkE2uhKxgDg/IKtfrmOeVtEWXsTV9PbdyUqqrNybju1q1FykLvq2x PMlRRCk0CnkcIteHvSuzpHRJVytMcOyQTI6QI= Received: by 10.114.209.1 with SMTP id h1mr221745wag.36.1224028823884; Tue, 14 Oct 2008 17:00:23 -0700 (PDT) Received: by 10.114.39.11 with HTTP; Tue, 14 Oct 2008 17:00:23 -0700 (PDT) Message-ID: Date: Tue, 14 Oct 2008 18:00:23 -0600 From: "Scott Marlowe" To: Chris Subject: Re: Drupal and PostgreSQL - performance issues? Cc: "Ang Chin Han" , pgsql-general@postgresql.org In-Reply-To: <48F51EB4.3090908@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> <200810122214.53558.uwe@oss4u.com> <20081013090228.248a665f@dawn.webthatworks.it> <20081014114011.0ebe495a@dawn.webthatworks.it> <8c8854360810140647n58abc9bend377e0e234dd39a9@mail.gmail.com> <8c8854360810140828p3b81bba0xac006f5565519981@mail.gmail.com> <48F51EB4.3090908@gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/582 X-Sequence-Number: 138831 On Tue, Oct 14, 2008 at 4:35 PM, Chris wrote: > >> Note this comment: >> /* >> * Queries sent to Drupal should wrap all table names in curly brackets. >> This >> * function searches for this syntax and adds Drupal's table prefix to all >> * tables, allowing Drupal to coexist with other systems in the same >> database if >> * necessary. >> */ >> That's an MySQL-ism for working around legacy hosting sites offering >> only a single MySQL db bogging postgresql down... > > No it's not. It's about being able to use a single db for multiple app's. > Either I do something like that, or I have to [hardcode] change schemas > after each connection because I only have a single db & a single db user.. > which postgres/oracle[I'm sure others] support but not mysql. 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. Also, Oracle and PostgreSQL support differing default schemas for individual users, so you can have connections pooled by user to go to a certain schema. > 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.