On 01/06/2017 05:32 AM, BRUSSER Michael wrote:
Thank you Torsten and Tom, this rang the bell and put me on the right track.
" This should be a can't-happen failure ..." - indeed, the wound is
self-inflicted.
Can you share what the cause was as history has shown that if one person
makes a mis
January 05, 2017 5:04 PM
To: Torsten Förtsch
Cc: BRUSSER Michael; pgsql-general@postgresql.org
Subject: Re: [GENERAL] psql error (encoding related?)
Torsten Fortsch writes:
> This hex string decodes to something sensible:
> $ perl -le 'print pack "H*", shift'
> 246c69
=?UTF-8?Q?Torsten_F=C3=B6rtsch?= writes:
> This hex string decodes to something sensible:
> $ perl -le 'print pack "H*", shift'
> 246c69626469722f757466385f616e645f69736f383835395f31
> $libdir/utf8_and_iso8859_1
> Maybe it rings a bell.
Hah, that's pretty suggestive. So probably, there's an enc
This hex string decodes to something sensible:
$ perl -le 'print pack "H*", shift'
246c69626469722f757466385f616e645f69736f383835395f31
$libdir/utf8_and_iso8859_1
Maybe it rings a bell.
On Thu, Jan 5, 2017 at 7:57 PM, BRUSSER Michael
wrote:
> I see this with PostgreSQL 9.4.7 and some 8.x vers
On 12/28/11 1:54 AM, hosuresh wrote:
I have installed postgresql-9.0 on my CentOS 6.0 server in the directory
/usr/pgsql-9.0/.
Its data directory resides in /var/lib/pgsql/9.0/
unable to run $psql dbname command
when i run the commands its showing the error like:
[root@CentOS-60-32-minimal ~]#
This message has been digitally signed by the sender.
Re___GENERAL__psql_error__psql__symbol_lookup_error__psql__undefined_symbol__PQconnectdbParams.eml
Description: Binary data
-
Hi-Tech Gears Ltd, Gurgaon, India
--
Sent via pgsql-general mailing list (pgsql-g
On Wed, 2011-12-28 at 01:54 -0800, hosuresh wrote:
>
> I have installed postgresql-9.0 on my CentOS 6.0 server in the
> directory
> /usr/pgsql-9.0/.
> Its data directory resides in /var/lib/pgsql/9.0/
>
> unable to run $psql dbname command
>
> when i run the commands its showing the error like:
Jeff Ross <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Hmm [ pokes around a bit... ] Do you perhaps have a higher debug
>> verbosity level on this machine than the others? I can't immediately
>> think of a reason why anything would be trying to print an untransformed
>> NULL constant, but it
Tom Lane wrote:
Jeff Ross <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Hmm. Can you try that with \set VERBOSITY verbose so we can determine
where the error is being thrown from?
psql:/tmp/people.sql:79: ERROR: XX000: unrecognized node type: 655
LOCATION: _outValue, outfuncs.c:1707
Hmm [
Tom Lane wrote:
Jeff Ross <[EMAIL PROTECTED]> writes:
When psql begins loading this file, it throws the error:
psql:/tmp/people.sql:79: ERROR: unrecognized node type: 655
Hmm. Can you try that with \set VERBOSITY verbose so we can determine
where the error is being thrown from?
Using t
Jeff Ross <[EMAIL PROTECTED]> writes:
> When psql begins loading this file, it throws the error:
> psql:/tmp/people.sql:79: ERROR: unrecognized node type: 655
Hmm. Can you try that with \set VERBOSITY verbose so we can determine
where the error is being thrown from?
> The interesting thing is
On Wednesday 13. June 2007 15:45, Tom Lane wrote:
>psql itself has no business touching the database directory, and a
> quick search of the source code shows no instance of "Cannot stat"
> anywhere in released PG sources.
>
>I think you are being burnt by some misbehavior of Debian's wrapper
>patch
Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> I have moved my database files from their default location to their own
> partition on with their own controller and disks. PostgreSQL works OK
> and I can connect with Pgadmin (Debian Lenny AMD64, PostgreSQL 8.2.4).
> When I want to connect with psq
Tom was right, on the Mac libreadline is linked to libedit.
My "solution" was to comment out the line reporting the
error in the program "input.c"
Jerry
On Nov 9, 2005, at 7:27 AM, Andreas Seltenreich wrote:
Tom Lane writes:
Jerry LeVan <[EMAIL PROTECTED]> writes:
I just upgraded from 8.0.4
Tom Lane writes:
> Jerry LeVan <[EMAIL PROTECTED]> writes:
>> I just upgraded from 8.0.4 to 8.1.0 this afternoon and the only thing
>> "bad" I have noticed is that whenever I quit psql I get a message:
>> could not save history to file "/Users/jerry/.psql_history": Invalid
>> argument
>> This is
Jerry LeVan <[EMAIL PROTECTED]> writes:
> I just upgraded from 8.0.4 to 8.1.0 this afternoon and the only thing
> "bad" I have noticed is that whenever I quit psql I get a message:
> could not save history to file "/Users/jerry/.psql_history": Invalid
> argument
> This is on MacOS X 10.4.3
The P
Some more info, the history is actually written!
( ' ' seems to be translated to \40 )
Still get the error message...
Jerry
Subject: psql error on quitting...
Hi,
I just upgraded from 8.0.4 to 8.1.0 this afternoon and the only thing
"bad" I have noticed is that whenever I quit psql I get a
"Kelvin T. Leung" <[EMAIL PROTECTED]> writes:
> Now, I am unable to run psql using my own OS login a/c. And I get an
> error message:
> psql: error while loading shared libraries: psql: undefined symbol:
> get_progname
This is a version-skew issue: you are trying to use a psql executable
w
"G. Frank Liu" <[EMAIL PROTECTED]> writes:
> $ psql -U gforge gforge
> psql: FATAL: Invalid page header in block 3 of pg_trigger_tgrelid_tgname_index
> Any ideas how I can fix it?
See the REINDEX man page. In 7.3 I think you have to go through the
full run-a-standalone-backend pushup to reindex
Phil Campaigne <[EMAIL PROTECTED]> writes:
> -bash-2.05b$ ldd /usr/local/pgsql/lib/libpq.so.3
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x4001d000)
> libresolv.so.2 => /lib/libresolv.so.2 (0x4004a000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x4005a000)
> libc.so.6 => /li
20 matches
Mail list logo
