Hi Roger,
Thanks for the explanation.
Collin
On 3/3/10 11:11 PM, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Collin Capano wrote:
>
>> Why does it prefer to use
>> /var/tmp or some other temp directory as opposed to just using the
>> current directory? Is there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collin Capano wrote:
> Why does it prefer to use
> /var/tmp or some other temp directory as opposed to just using the
> current directory? Is there some performance advantage in doing this?
The temp tables are for a particular connection only. If
Hi all,
Thanks so much for the info! The problem does appear to have been due to
temp_store_directory. It was set to /var/tmp; on our clusters /var/tmp
exits on another disk which only has about 3GB free as opposed to the
3TB I have on the disk that the database lives on. I re-set it the
On Wed, Mar 03, 2010 at 12:57:22AM -0500, Collin Capano scratched on the wall:
> Hello SQLite users,
>
> I've been running into some disk I/O errors when doing things such as
> vacuuming and/or inserting things into temp tables in a database.
Both of those operations require temp space.
On Mar 3, 2010, at 12:57 PM, Collin Capano wrote:
> Hello SQLite users,
>
> I've been running into some disk I/O errors when doing things such as
> vacuuming and/or inserting things into temp tables in a database. The
> databases that are giving me trouble are quite large: between 29 and
> 55GB.
On Wed, Mar 3, 2010 at 8:57 AM, Collin Capano wrote:
> The databases in question don't seem to be
> corrupt; I can open them on the command line and in python programs
> (using pysqlite) and can read triggers from them just fine. It's just
> when I try to vacuum and
On 3 Mar 2010, at 5:57am, Collin Capano wrote:
> I've been running into some disk I/O errors when doing things such as
> vacuuming and/or inserting things into temp tables in a database. The
> databases that are giving me trouble are quite large: between 29 and
> 55GB. However, as large as
Hello SQLite users,
I've been running into some disk I/O errors when doing things such as
vacuuming and/or inserting things into temp tables in a database. The
databases that are giving me trouble are quite large: between 29 and
55GB. However, as large as that is, I don't think running out of
8 matches
Mail list logo