"Rod Taylor" <[EMAIL PROTECTED]> writes:
> 7.2 crashes with the below function:
> CREATE OR REPLACE FUNCTION runMaintenance()
> RETURNS BOOL AS '
> VACUUM;
> SELECT TRUE;
> ' LANGUAGE sql;
Ugh. The problem is that VACUUM's implicit CommitTransaction calls
wipe out all the transient memory a
Daniel Malaquias de Freitas <[EMAIL PROTECTED]> writes:
> I tried to store 700GB of ".tif" images but postgreSQL didn´t support it.
> Well. Actually I´d like to know if postgreSQL supports it in multiples HD,
> since today´s HD support up to 200 GB only.
Use RAID or LVM to build as big a filesyst
Hi,
POSTGRESQL BUG REPORT TEMPLATE
Your name : Deric Sullivan
Your email address : [EM
> A lot of this looks like problems with configure using the wrong cpp
> to do C preprocessor tests. In particular the syntax errors in the
I tried setting it manually and that fixed it. I couldn't get configure
to work using either method of getting at MIPSpro's preprocessor (/lib/cpp
and /usr
7.2 crashes with the below function:
CREATE OR REPLACE FUNCTION runMaintenance()
RETURNS BOOL AS '
VACUUM;
SELECT TRUE;
' LANGUAGE sql;
I was going to toss a bunch of system maintenance stuff in a database
function to make administration for those who administer the boxes
(not me -- I just t
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the proble
> Attached is a patch against current CVS that fixes both of the known
> problems with sequences: failure to flush XLOG after a transaction
Great! Thanks... and sorry for missing these cases year ago -:)
Vadim
---(end of broadcast)---
TIP 1: subsc
> Sample Code
> SELECT time('10:10');
Read the release notes to see that this is no longer allowed, to allow
other SQL9x features to be implemented.
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
POSTGRESQL BUG REPORT
Your name :Viacheslav N Tararin
Your email address :[EMAIL PROTECTED]
System
> But sequences should not be under transaction control. Can you
> safely rollback a sequence? No! The only way to ensure that would
...
> Placing a restriction on an application that says it must treat the values
> returned from a sequence as if they might not be committed is absurd.
Why? The
Hi,
- I tried to execute following SQL alter table PRICEGROUP add FOREIGN KEY ("PARENT") REFERENCES "PRICEGROUP" ON DELETE CASCADE
this gives an error ALTER TABLE: column "PARENT" referenced in foreign key constraint does not exist (7) while I'm sure that the column exists and is Non null. I'm
> > This isn't an issue for a SELECT nextval() standing on
> > its own AFAIK the result will not be transmitted to the
> > client until after the commit happens. But it would be
> > an issue for a select executed inside a transaction
> > block (begin/commit).
>
> The behavior of SELECT nextval()
I tried to store 700GB of ".tif" images but postgreSQL didn´t support it.
Well. Actually I´d like to know if postgreSQL supports it in multiples HD,
since today´s HD support up to 200 GB only.
---(end of broadcast)---
TIP 3: if posting/reading thro
I noticed a message asking if this scenario was consistent with the
other reports, and yes it is. We have seen this occuring on our system
with versions as old as 7.0.
Glad to see someone has finally nailed this one.
Dave
---(end of broadcast)---
14 matches
Mail list logo
