------=_Part_2851_27612703.1212677481561
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
Consider this simple case:
postgres=# TRUNCATE foo, foo;
ERROR: cannot TRUNCATE "foo" because it is being used by active queries
in
this session
The above occurs because the ExecuteTruncate() function invokes
truncate_check_rel() in a loop. Since the same table name appears twice,
the
rd_refcnt for table "foo" is bumped up to 2, causing the above failure.
We might want to add a step to ExecuteTruncate(), or whatever calls it, to
make the list unique.
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
------=_Part_2851_27612703.1212677481561
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi, <br><br>Consider this simple case:<br><br>postgres=# TRUNCATE foo,
foo;
<br>ERROR: cannot TRUNCATE "foo" because it is being used
by active queries
in this session
<br>
<br>The above occurs because the ExecuteTruncate() function invokes
truncate_check_rel() in a loop. Since the same table name appears twice,
the rd_refcnt for table "foo" is bumped up to 2, causing the
above failure.<br>
<br clear="all">We might want to add a
step to ExecuteTruncate(), or whatever calls it, to make the list
unique.<br><br>Regards,<br>Nikhils<br>-- <br>EnterpriseDB <a
href="http://www.enterprisedb.com">http://www.enterprisedb.com</a>
------=_Part_2851_27612703.1212677481561--
|
