that is how i have it set up. first, a vacuum. next line in the script is
a "select. . .not in" query that takes forever. cron executed the first
(the vacuum) and then immediatly executed the second (the select), so both
the vacuum and the select were running at the same time. needless to sa
Hi !
I'm compiling (really trying) postgresql 6.5.2 on a Sun with sunos 5.5.1, I
have run the configure scripts with the next options:
./configure --prefix=/export/home/moises/psql --with-ODBC
--with-CC=/usr/local/bin/gcc --with-CXX=/usr/local/bin/g++
and then i do 'make', after some binaries
JT Kirkpatrick wrote:
>
> i'm trying to run a query at night, and output the results to a file. i
> think i have the syntax right for the proper output, but it now appears
> that my little automatic (cron) query ran IMMEDIATELY after the first
> command in the same cron file (a VACUUM of the sam
i'm trying to run a query at night, and output the results to a file. i
think i have the syntax right for the proper output, but it now appears
that my little automatic (cron) query ran IMMEDIATELY after the first
command in the same cron file (a VACUUM of the same database) executed. it
did
