Thank you much for such a precise explanation. That was very helpful.
Regards,
Radhika
On 10/2/07, Scott Marlowe <[EMAIL PROTECTED]> wrote:
>
> On 10/2/07, Radhika S <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have recently had to change our nightly jobs from running vacuum
> > full, as it has c
On Tue, 2 Oct 2007 21:45:37 -0400
"Radhika S" <[EMAIL PROTECTED]> wrote:
> But this has bought me to the question of what exactly is the
> difference between vacuum and vacuum full. If both give back free
> space to the disk, then why have vacuum full.
Not quite. "VACUUM FULL" returns space to th
On 10/2/07, Radhika S <[EMAIL PROTECTED]> wrote:
> ... why have vacuum full...
See:
http://www.postgresql.org/docs/8.2/static/routine-vacuuming.html
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
On 10/2/07, Radhika S <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have recently had to change our nightly jobs from running vacuum
> full, as it has caused problems for us. Upon doing more reading on
> this topic, I understand that vacuum full needs explicit locks on the
> entire db and explicit locking
Hi,
I have recently had to change our nightly jobs from running vacuum
full, as it has caused problems for us. Upon doing more reading on
this topic, I understand that vacuum full needs explicit locks on the
entire db and explicit locking conflicts with all other locks.
But this has bought me to
