On Wed, Jun 11, 2008 at 11:17 AM, Hiroshi Inoue <[EMAIL PROTECTED]> wrote:
>> Tagables.Parameters(0) = oldtags("devicetype")
>> Set tagableRS = Tagables.Execute
>> tagableid = tagableRS("tagableid").Value
>
> Please add
> tagableRS.Close()
Your advice worked perfec
Joshua D. Drake wrote:
On Wed, 2008-06-11 at 09:36 +1000, Devendra Singh Rawat wrote:
Hi,
We are using PostgreSQL 7.4.5 and facing issues with increasing disk space
...I would also suggest strongly you update to the latest 7.4 dot release.
But as always read all the release n
On Wed, Jun 11, 2008 at 1:42 AM, Devendra Singh Rawat
<[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I recreated my database this morning with a dump size of 3GB, which after
> database creation occupied 3.5GB on disk.
> And in less than 8 hours it has bloated to additional 3.7GB (the disk size
> now i
Oops! Sorry. I meant to do that!
Carol
On Jun 10, 2008, at 3:29 PM, Alvaro Herrera wrote:
Carol Walter wrote:
I'm not sure I fully understand what your saying, but I had a similar
problem with items appearing to be dropped but weren't. I had
accidentally created them in template1. Once I
Devendra Singh Rawat wrote:
Hi All,
I recreated my database this morning with a dump size of 3GB, which after
database creation occupied 3.5GB on disk.
And in less than 8 hours it has bloated to additional 3.7GB (the disk size now
is 7.2GB).
There are quite a few DML operations which are happ
On Wed, Jun 11, 2008 at 1:12 PM, Devendra Singh Rawat
<[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I recreated my database this morning with a dump size of 3GB, which after
> database creation occupied 3.5GB on disk.
> And in less than 8 hours it has bloated to additional 3.7GB (the disk size
> now i
Hi All,
I recreated my database this morning with a dump size of 3GB, which after
database creation occupied 3.5GB on disk.
And in less than 8 hours it has bloated to additional 3.7GB (the disk size now
is 7.2GB).
There are quite a few DML operations which are happening on my DB.
SELECT relnam
