Hi,
if you're using a pg version prio to 8.0 your pitfall might also be
a conversion between int and bigint datatypes.
So if you're doing somthing like
SELECT a.x, b.y, c.y FROM a, b WHERE a.x = b.x;
and a.x is INT4 and b.x is INT8 (or BIGINT) the planner counts this as
a data conversion and uses a
Hi Simon,
Actually, me too. Never saw the need for the Oracle command myself.
It actually has. If you want to move your redo logs to a new disk, you
create a new redo log file and then issue a ALTER SYSTEM SWITCH LOGFILE;
to switch to the new logfile. Then you can remove the "old" one
(speaking jus
what. Allowing that to be turned off would be interesting for a number
of purposes, such as burning a database onto CD.
FWIW, Oracle suggests a "transportable tablespace" for this feature.
Which is a tablespace that is not written too and which can be read by
any database.
Would that solve the pur
dexes etc.).
I'll try to make a patch if you'd agree that this information is
"missing".
Greetings, Klaus
--
Full Name : Klaus Naumann | (http://www.mgnet.de/) (Germany)
Phone / FAX : ++49/177/7862964 | E-Mail: ([EMAIL PROTECTED])
---
On Thu, 8 Jul 2004, Jonah H. Harris wrote:
Hi,
> 3. The maximum quota size is (currently) the maximum of int4*1024 bytes.
why is this? This is very limiting ...
Using a 64bit value would be a lot more straight foreward.
Greetings, Klaus
--
Full Name : Klaus Naumann | (h
now
on could save a lot of work in the future ...
> It sounded to me like it might be a limitation forced by some other part
> of postgres, but I don't really know... Good question though.
I'm not sure about it either - anyone?
Greetings, Klaus
--
Full Name : Klaus Naumann
r
>
>
>
>
>
>
>
>
> ---(end of broadcast)---
> TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/docs/faqs/FAQ.html
>
&
