Bas Scheffers writes:
> When opening a file in psql, ~ (the user's home dir) is resolved when
> using tab completion to find the file, but when you hit enter and psql
> actualy tries to open it, you get a file not found error.
This is not a bug. If there is not file named ~ then it can't be open
Peter Eisentraut wrote:
> Bas Scheffers writes:
>
> > When opening a file in psql, ~ (the user's home dir) is resolved when
> > using tab completion to find the file, but when you hit enter and psql
> > actualy tries to open it, you get a file not found error.
>
> This is not a bug. If there is
On Thu, 2003-10-30 at 13:13, Peter Eisentraut wrote:
> Bas Scheffers writes:
>
> > When opening a file in psql, ~ (the user's home dir) is resolved when
> > using tab completion to find the file, but when you hit enter and psql
> > actualy tries to open it, you get a file not found error.
>
> Thi
sir
we have tried for the last 3 months for installing postgress beta4 version on windows
98 but we are unable to start the postmaster.
please give step by step procedure for postgres on windows 98.
thnaking you
k.kedar
Peter Eisentraut said:
> This is not a bug. If there is not file named ~ then it can't be
> opened.
I am not trying to open a file named ~, I am using it as part of a file
name, ie: ~/ewap/sql/ewap.sql. (where ~=/home/bas) This is perfectly valid
on any unix system and especialy since tab completi
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> Bas Scheffers writes:
>>> When opening a file in psql, ~ (the user's home dir) is resolved when
>>> using tab completion to find the file, but when you hit enter and psql
>>> actualy tries to open it, you get a file not found er
ljb <[EMAIL PROTECTED]> writes:
> [Using PostgreSQL-7.3.4 and -7.4beta5, Tcl-8.4.x.]
> Binary data written to a Large Object with libpgtcl's pg_lo_write is
> corrupted. Tcl is mangling the data - something to do with UTF-8
> conversion. Example: 0x80 becomes 0xc2 0x80, and 0xff becomes 0xc3 0xbf.
On Tue, Oct 28, 2003 at 04:48:59PM -0500, Tom Lane wrote:
> AFAICT there was no discussion about this issue when the patch was
> proposed and applied. But now that the point is raised I have to say
> that I don't like this change. I don't think system catalogs should be
> excluded from tab compl
AFAICT there was no discussion about this issue when the patch was
proposed and applied. But now that the point is raised I have to say
that I don't like this change. I don't think system catalogs should be
excluded from tab completion. They never were before 7.4, and I have
not seen anyone com
On Tue, 28 Oct 2003, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I say leave it the way it is. If you want system table tab completion,
> > simply:
> > ALTER USER ... SET search_path =3D pg_catalog,...;
>
> Unfortunately, that *does not* affect the tab-completion behavior
On Tue, 28 Oct 2003, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > Is it possible to remove the implicit search path of pg_catalog from a
> > psql session without it breaking lots of stuff?
>
> Do you consider "+", "count()", etc to be important stuff?
Me, hardly ever use th
11 matches
Mail list logo