Hello List,
I have done some searching and looking at all the documentation I
could find, and I have found a (what i consider) a bug in pg_dump
pg_restore that I wanted to bounce off the list to find their
solutions.
I have a database which gets updated from many locations and it looks
like we ha
SELECT book.title, book.author, book.feedback
FROM postgresql_admin_community
JOIN books ON book.subject ILIKE '%postgres%'
JOIN readings ON readings.reader_id = postgresql_admin_community.id
WHERE
postgres_admin_community.user_experience_level = 'I have spent years
around databases, but never real
Hello all,
I tried in vain last night to move the pg_xlog directory to another
drive to get some more speed out of our database.
To do this, I used linkd.exe from the Windows Server 2003 Resource
Kit. This tool creates a 'junction' (which is the Windows term for
symlink).
However, with the pg_x
Hey all, I posted this over on the EDB forums as well, no answers yet, so I
am trying here.
I am trying to set up a pg_dump between a postgresql 8.3.1 server and edb
8.3 server.
This is to get slony working between the two.
When I do:
pg_dump -s -U testmaster -h 10.0.0.1 -p 5444 testuser | psql
Hi all,
I am importing a bunch of data exported from an Oracle database.
This came out as a flat file, tab delimited.
I have parsed this through a ruby script that does the following:
For each line
split it at the tab
for each column
parse it through Iconv and convert from UTF8 to UTF8
> Anyone got any ideas how I can hunt down what is in this row, visually
> looking at it hasn't helped?
As a followup, I am getting this same sort of error at various points
on the file.
So I tried taking the line, and cleaning it with Iconv and turning it
into an ASCII sequence and inserting it
OK, I'm mailing the list the results of my problem so future people can find it.
The error was
ERROR: invalid byte sequence for encoding "UTF8": 0xa2
with many different types of 0x... lines.
The problem was indeed a bug, but one that sat between the keyboard
and screen (that is, me), not with
On Fri, Sep 19, 2008 at 6:29 PM, Tore Halset <[EMAIL PROTECTED]> wrote:
> Looks like I have managed to insert an illegal character into the main
> system that does not conform to UTF-8. Anything I can and should do to work
> around this issue?
I have had the same problem previously and after a lot
On Fri, Sep 26, 2008 at 7:12 PM, Tore Halset <[EMAIL PROTECTED]> wrote:
> Thanks a lot! Using the script, I found the entries with invalid UTF-8 and
> fixed them in the database.
That's great news. You are welcome.
Curious, how long did it take to run on your entire table? You
mentioned it was
