From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Jozef Ševčík <sevcik(at)styxsystems(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Quoting table/column names vs performance |
Date: | 2008-04-09 15:48:53 |
Message-ID: | 47FCE565.7070608@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jozef Ševčík wrote:
> Hi all,
>
> I just switched from MS SQL to PostgreSQL on project and have
> question about double-quoting names of fields/tables regarding to
> performance.
If the cost of quoting column-names is a significant part of your query
costs, you must have some very fast queries. I would not worry.
> In MSSQL I had something like: SELECT Column1,Column2 from MyTable
>
> In PgSQL I write: SELECT "Column1", "Column2" from "MyTable"
>
> Which is fine and working, I have no doubt about it. I'm just
> guessing if this does not affect performance in any way. I know I may
> rename tables/fields to lowercase and avoid double-quotting, but it
> double-quotting has no affect on perf. is it worth it ? Or are there
> any advantages of using 'non-quoted' identifiers agains double-quoted
If you double-quote identifiers when you create them you'll want to
double-quote them everywhere they are used. That's OK with a new sytem,
but can be awkward if you have a lot of existing code that isn't already
quoted.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Jozef Ševčík | 2008-04-09 15:55:31 | Re: Quoting table/column names vs performance |
Previous Message | Markus Wollny | 2008-04-09 15:47:44 | Re: tsvector_update_trigger throws error "column is not of tsvector type" |