Re: asynchronous psql command options?

Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 17G 2.0G 13G 13% /var/lib/pgsql/data
/dev/sdd1 17G 11G 5.2G 68% /datadir

correct disk space ran out. However, just one more question... on my test server the indexes are ~8G. I moved the data to be indexed (sym linkd ) to the datadir (as shown above). I thought that the indexes would be in my /var/lib/pgsql/data directory.

How can I get the indexes on a disk with necessary space. Please help!

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:Christopher Smith writes:
> i used psql via ssh on dial-up and closed the ssh client. I logged in
> again and it showed that the postmater process was still running.. I
> thought that the index building process would continue 'til
> completion.

> however, this morning no indexes were built. Is it possible to send
> commands via psql asynchronous. Does anyone know why the index
> building process stopped?

It worked for me in a quick test here: issue CREATE INDEX command,
"kill -9" the psql client from another window, wait for indexing to
finish.

I wonder whether you had started a transaction block, viz
begin;
create index ...;
<>
Without a commit to match the begin, the index would be discarded.

Another likely prospect is that the CREATE INDEX command actually failed
(ran out of disk space, for example). Did you look in the postmaster
log to see if any error message was recorded?

regards, tom lane

---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now