Re: [ADMIN] Vacuum Full

2009-04-02 Thread Tino Schwarze
Hi Tom, On Wed, Apr 01, 2009 at 08:58:54PM -0400, Tom Lane wrote: > >> Maybe we should remove the code and make > >> VACUUM FULL do the table-rewrite thing. > > > What do you mean with "the table-rewrite thing", exactly? > > Like CLUSTER, except not bothering to sort the rows: just seqscan the

Re: [ADMIN] Vacuum Full

2009-04-02 Thread Alvaro Herrera
Tino Schwarze wrote: > I remember several people (including myself) who used VACUUM FULL as a > last resort when their database was bloated and they run out of disk > space. But this seems to be moot, anyway, so it's probably better not to > offer something that might or might not work in such a s

[ADMIN] postgresql 8.4

2009-04-02 Thread Ben Kim
I'm planning to upgrade. Is there a updated release schedule for 8.4? Thanks. Ben Kim -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin

Re: [ADMIN] Vacuum Full

2009-04-02 Thread Kevin Grittner
Alvaro Herrera wrote: > rare enough that we can suggest other workarounds when need arises. Yeah, I can't remember ever being glad I tried a VACUUM FULL. I think I once allowed it a week and a half to try to finish in a situation where there wasn't enough disk space for a rewrite (CLUSTER or t

Re: [ADMIN] Vacuum Full

2009-04-02 Thread Alvaro Herrera
Kevin Grittner wrote: > Yeah, I can't remember ever being glad I tried a VACUUM FULL. I think > I once allowed it a week and a half to try to finish in a situation > where there wasn't enough disk space for a rewrite (CLUSTER or the > clever side-effect trick with ALTER TABLE). I even dropped al

Re: [ADMIN] postgresql 8.4

2009-04-02 Thread Kenneth Marshall
On Thu, Apr 02, 2009 at 08:55:48AM -0500, Ben Kim wrote: > > I'm planning to upgrade. Is there a updated release schedule for 8.4? > > > Thanks. > > Ben Kim > Ha, ha, ha, ha... That's a good one. Seriously, we have not even started beta testing. Cheers, Ken -- Sent via pgsql-admin mailing list

Re: [ADMIN] postgresql 8.4

2009-04-02 Thread Tom Lane
Ben Kim writes: > I'm planning to upgrade. Is there a updated release schedule for 8.4? [ all together now... ] "When it's ready!" At this point an informed guess would be "sometime this summer", but it's strictly a guess. regards, tom lane -- Sent via pgsql-admin mai

Re: [ADMIN] postgresql 8.4

2009-04-02 Thread Ben Kim
I guess I asked it the wrong way at the wrong time... (in the cross-fire of jokes). With today's post about the vacuum full ("in 8.4 with the dead space map ..." ), I was checking when 8.4 is coming out but these were all I could find. http://developer.postgresql.org/index.php/PostgreSQL_8

Re: [ADMIN] postgresql 8.4

2009-04-02 Thread Scott Marlowe
On Thu, Apr 2, 2009 at 12:41 PM, Ben Kim wrote: > > I guess I asked it the wrong way at the wrong time... (in the cross-fire of > jokes). Best way to gauge this stuff is to trawl through the -hackers and associated lists. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make

[ADMIN] Text Description of Current Exception

2009-04-02 Thread Ward Eaton
Hello, I would like to log any exceptions which may be thrown in my database functions. Oracle has a predefined variable, SQLERRM, which will always have a text description of the current exception. Is there anything like this available in postgres? Thank you, Ward Eaton Project Enginee

[ADMIN] how to do prefix_range default value?

2009-04-02 Thread Tony Liao
hi,all I have installed prefix contrib,it works well. now I want to insert default value [] to prefix column,because if the prefix column is NULL,the returns are not I want (with prefix @>'text').I alter column prefix default [],it return error: ERROR: syntax error at or near "[" LINE 2:

Re: [ADMIN] Text Description of Current Exception

2009-04-02 Thread Justin
Ward Eaton wrote: Hello,   I would like to log any exceptions which may be thrown in my database functions.  Oracle has a predefined variable, SQLERRM, which will always have a text description of the current exception.  Is there anything like this available in postgres?