From: | Andreas Wenk <a(dot)wenk(at)netzmeister-st-pauli(dot)de> |
---|---|
To: | Michael Wood <esiotrot(at)gmail(dot)com> |
Cc: | john shipley <johnwshipley(at)hotmail(dot)co(dot)uk>, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Location of databases |
Date: | 2009-07-28 09:56:42 |
Message-ID: | 4A6ECB5A.5080305@netzmeister-st-pauli.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Michael Wood schrieb:
> 2009/7/28 Andreas Wenk <a(dot)wenk(at)netzmeister-st-pauli(dot)de>:
>> john shipley schrieb:
> [...]
>>> In order to load the contents of a PostgreSQL file into PSPP,
>>> I have to show its location and name and indicate that is is a PostgreSQL
>>> file by means of a statement like the following:
>>>
>>> FILE = /home/myusername/.../.../.../ filenamedb(PSQL).
>
> I don't know anything about PSPP, but you cannot directly access the
> files used by PostgreSQL. You have to use a client like psql or
> ODBC/JDBC or the PostgreSQL client libraries to talk to PostgreSQL and
> PostgreSQL reads/writes the files itself. This is why the location of
> the files is generally not something you need to know. What you do
> need to know is things like the IP address of the machine running
> PostgreSQL and the port number that PostgreSQL is running on (unless
> you're on the same machine and you're using a Unix domain socket to
> talk to PostgreSQL.)
hm - I think you are right. So maybe this PSPP is not working with a database like PG at
all. Or something else has to be set up.
My focus was more to show where the files and direcotries are located generally. Maybe
this was not helping to find a solution ...
Cheers
Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Petros Thespis | 2009-07-28 11:15:42 | Select from second table only if select from first returns no results |
Previous Message | Andreas Wenk | 2009-07-28 09:50:58 | Re: Understanding the output of EXPLAIN ANALYSE |