Surely the windows installation of psql ought to be set up to work with the
terminal already?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-6246-character-encoding-for-64-bit-tp4888531p4902052.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
I think I've figured it out - thanks all for your help. Craig Ringer appears
to be right.
>From documentation for psql 9.1 under Usage>Connecting to a database
"If at least one of standard input or standard output are a terminal, then
psql sets the client encoding to "auto", which will detect the
On Fri, Oct 14, 2011 at 12:29 AM, Vishnu S. wrote:
> The application deletes the contents of tables in the tablespace using
> DELETE TABLE query.
There's no DELETE TABLE command. Do you mean DELETE, or DROP TABLE?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreS
How about a warning in docs for uncautious DBA's?
2011/10/13 Bruce Momjian
>
> I assume this should _not_ be added as a TODO.
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
> \copy is different because it uses OT_WHOLE_LINE mode to read the
> argument, and that doesn't expand :variable references. I'd be a bit
> leery of changing that.
So, doc warning then?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bu
Josh Berkus wrote:
>
> > \copy is different because it uses OT_WHOLE_LINE mode to read the
> > argument, and that doesn't expand :variable references. I'd be a bit
> > leery of changing that.
>
> So, doc warning then?
I don't think enough people have hit this problem to warrant that.
--
Bru
