| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Darren Duncan <darren(at)darrenduncan(dot)net> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, mike beeper <mbeeper(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Creating temp tables inside read only transactions |
| Date: | 2011-07-11 13:17:10 |
| Message-ID: | 2442397E-2BD5-424E-AF2E-E1F4CDCDA6EB@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Jul8, 2011, at 08:21 , Darren Duncan wrote:
> Also, the proper way to do temporary tables would be to put them in
> another database than the main one, where the whole other database
> has the property of being temporary.
FWIW, Microsoft SQL Server does it that way, and as a result temporary
tables are severely restricted in a number of ways.
For example, custom datatypes defined in a non-temporary database
cannot be used in temporary table definitions, because datatypes may
only be used within the database they're defined in. You can of course
re-define the data type in the temporary database, but then obviously
have to do so every time you start new session because you start out
with an empty tempdb.
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2011-07-11 14:11:07 | Re: Schema for Website Comments |
| Previous Message | David Johnston | 2011-07-11 13:10:57 | Re: [HACKERS] Creating temp tables inside read only transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2011-07-11 14:12:17 | Re: [HACKERS] Creating temp tables inside read only transactions |
| Previous Message | David Johnston | 2011-07-11 13:10:57 | Re: [HACKERS] Creating temp tables inside read only transactions |