nuary 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 <tfoertsch...@gmail.com> writes:
> This hex string decodes to something sensible:
>
I see this with PostgreSQL 9.4.7 and some 8.x versions running on Linux Red Hat.
Older versions "supposedly" do not exhibit this behavior, but I didn't check.
$ psql
Password:
psql: FATAL: could not access file
"\x246c69626469722f757466385f616e645f69736f383835395f31": No such file or
directory
-Original Message-
From: Albe Laurenz [mailto:laurenz.a...@wien.gv.at]
Sent: Thursday, June 16, 2011 5:16 AM
To: BRUSSER Michael; pgsql-general@postgresql.org
Subject: RE: [GENERAL] Invalid byte sequence for encoding UTF8: 0xedbebf
BRUSSER Michael wrote:
Is there a way to find
This is a follow-up on my previous message
http://archives.postgresql.org/pgsql-general/2011-06/msg00054.php
I think I have now some understanding of what's causing the problem, but I
don't have a good solution, instead more questions.
The release notes for v8.1 at
, 2011 01:18:27 PM BRUSSER Michael wrote:
Unless there's no other options I don't want to use sed or break file into
pieces, if possible,
--
iconv loads everything into RAM. You can use split, convert the pieces, and
then recombine, I did that when
We upgrading some old database (7.3.10 to 8.4.4). This involves running
pg_dump on the old db
and loading the datafile to the new db. If this matters we do not use
pg_restore, the dump file is just sourced with psql,
and this is where I ran into problem:
psql: .../postgresql_archive.src/...
I would appreciate some pointers on using database encoding and locale.
This is the error message I get from initdb, on Sun Solaris 5.10:
initdb: encoding mismatch
The encoding you selected (UTF8) and the encoding that the
selected locale uses (LATIN1) do not match. This would lead to
From: BRUSSER Michael
Sent: Wednesday, May 19, 2010 10:06 AM
To: 'pgsql-general@postgresql.org'
Subject: TCL client interface
Did anyone successfully integrate the TCL client library from
http://pgfoundry.org/projects/pgtcl/ ?
Even more helpful would be if someone did this on Solarix
Did anyone successfully integrate the TCL client library from
http://pgfoundry.org/projects/pgtcl/ ?
Even more helpful would be if someone did this on Solarix-x86, building
a 64-bit binaries.
Thanks,
Michael.
This email and any attachments are intended solely for the use of the
No, I still don't know whats being written.
I have tried to isolate it, and checked several folders, but can't
find the path.
I don't do much on Windows, but when I needed to associate
Folks,
I ran the build on a different Solaris machine and installation
immediately failed with this message:
ld.so.1: postgres: fatal: libresolv.so.2: version `SUNW_2.2.2' not found
(required by file .../some-path/postgres)
Looking at the build machine:
/usr/lib /usr/ccs/bin/elfdump -v
Some time ago I had a similar problem with Postgresql 7.3.
If I remember correctly running pg_resetxlog helped; check out
http://www.postgresql.org/docs/8.3/static/app-pgresetxlog.html
Michael.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mary Ellen
There is probably a better way of doing this, but if nothing else try
this:
PostgreSQL executables on Unix:
% file postmaster psql
postmaster: ELF 32-bit MSB executable SPARC Version 1, dynamically
linked, not stripped
psql:ELF 32-bit MSB executable SPARC Version 1, dynamically
How would you like to use a database that has nuances like these --
http://forums.mysql.com/read.php?20,141120,141120#msg-141120
---
Huh?
A blank string (does that mean '' or ' '?) is not NULL, so of
*course* it should pass the NOT NULL constraint.
Or am I missing something?
---
I
Zeroing out the whole block containing it is the usual recipe.
Something like this worked for me in the past:
% dd bs=8k count=X /dev/zero clog-file
I had to calculate X, because I usually had a situation with truncated
clog-file, and a failed attempt to read it from offset XYZ.
And I
The management of the IPC resources on Solaris 10 has changed
(it now involves the /etc/project file)
I wonder if someone can point me to a white-paper or any other
information
for configuring shared resources (semaphores, shared memory, etc) for
Postgresql on Solaris 10.
Thanks,
Michael.
16 matches
Mail list logo
