Re: Vacuum behaviour in plpgsql function

From: "Alain Lavigne" <alavigne(at)zaq(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vacuum behaviour in plpgsql function
Date: 2002-06-04 11:57:39
Message-ID: C34466F5BBA39949A8F5C180022EC206151DF5@zaq-msg-03.corp.zaq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Tom, I didn't know. I will find another way to do it.

----------------------------------------------------------------------------------------
Alain Lavigne - Data Administrator - ZAQ Interactive Solutions E-Mail: alavigne(at)zaq(dot)com
297 St-Paul, West - Montreal, Quebec, Canada - H2Y 2A5
Phone: 514-282-7073 ext: 371 - Fax: 514-282-8011

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: June 3, 2002 19:41
To: Alain Lavigne
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Vacuum behaviour in plpgsql function

"Alain Lavigne" <alavigne(at)zaq(dot)com> writes:
> Using the function pgstatuple I want to use this to control what gets
> vacuumed.

You can't run VACUUM from inside a function because of memory-management
limitations. In current sources there is an error check to prevent you
from trying.

regards, tom lane

Browse pgsql-general by date

  From Date Subject
Next Message zze-Synchro ball001 exterieur FTRD 2002-06-04 13:32:23 Connexion with jdbc
Previous Message Martijn van Oosterhout 2002-06-04 07:53:34 Re: View vs. Statement Query Plan