Search Postgresql Archives

Re: TRUNCATE - timing of the return of disk space - caused by long-lived client?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Vince Negri" <vnegri@xxxxxxxxxxxxxxxxxxxxx> writes:
> What causes the file handles of the truncated table to be released by all postmaster processes?

It should happen when the other backends process the sinval message
about the TRUNCATE, which at the latest should be the next time they
begin command execution.  What were the other clients doing, just
sitting idle?

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux