Re: [ADMIN] evil characters #bfef cause dump failure

2004-11-16 Thread Markus Bertheau
Ð ÐÐÐ, 15/11/2004 Ð 20:34 -0500, Tom Lane ÐÐÑÐÑ: > "Iain" <[EMAIL PROTECTED]> writes: > > It seems that this kind of thing pops up from time to time. I don't have v8 > > available right now to check, but is SQL_ASCII still the default DB > > encoding? I'm wondering is unicode wouldn't be a better

Re: [ADMIN] evil characters #bfef cause dump failure

2004-11-16 Thread Iain
Hi, Recall that in 8.0 the default encoding will be derived from the locale. So if the postgres account has a reasonable locale set (presumably chosen somewhere during the system installation), everything will work out. That's seems pretty reasonable, though I think that standardizing on unicode (

Re: [ADMIN] evil characters #bfef cause dump failure

2004-11-16 Thread Peter Eisentraut
Am Dienstag, 16. November 2004 09:45 schrieb Iain: > That's seems pretty reasonable, though I think that standardizing on > unicode (and I guess that means UTF-8) is really the way to go. It was > designed as the universal standard after all. It may have been designed that way, but it is a failure

Re: [ADMIN] evil characters #bfef cause dump failure

2004-11-16 Thread Iain
Hi Peter, I know that the unicode standards are far from perfect, but I'm wondering why you consider it a failure. Is it technical, or just an acceptance thing? From my personal perspective, I never had any interest in such things as encodings or internationlization until I started working in Ja

Re: [ADMIN] evil characters #bfef cause dump failure

2004-11-16 Thread Peter Eisentraut
Am Dienstag, 16. November 2004 11:27 schrieb Iain: > I know that the unicode standards are far from perfect, but I'm wondering > why you consider it a failure. If it were a success, then everyone would be using it and we wouldn't have this discussion. Certainly, Unicode is reasonable and the bes

[ADMIN] Query failed: ERROR: Unable to identify an operator '=' for types 'character varying' and 'character'

2004-11-16 Thread Francisco Jose Bernabe Pellicer
Hello everybody, I'm working with a monitoring tool for Grid enviroments. The thing is that, this tool (GridICE) works uses a PosgreSQL Database. I get an error at this part of the code: $siteName = $_GET["siteName"]; $VONa

Re: [ADMIN] evil characters #bfef cause dump failure

2004-11-16 Thread Christian Fowler
I strongly agree with this. I have always been uncomfortable selecting "UNICODE" and never quite sure if it is the UTF8, UTF16, or UTF32 encoding. SQL_8BIT or SQL_RAW make much more sense than SQL_ASCII given that Tom said this is a lack of encoding. I fear I might have high-bits chopped off o

Re: [ADMIN] cannot open segment 1 of relation .... No such file or directory

2004-11-16 Thread ogjunk-pgjedan
Hello, --- Tom Lane <[EMAIL PROTECTED]> wrote: > <[EMAIL PROTECTED]> writes: > > I'm using PG 7.3.4 under RedHat 9.0 and I've started noticing the > > following type of errors: > > cannot open segment 1 of relation url (target block 537329664): > No > > such file or directory > > If this is co

[ADMIN] How to use custom functions created by my2pg.pl?

2004-11-16 Thread Scott Chapman
The my2pg.pl script creates custom functions that help with the MySQL "set" column type. I can't figure out how to use the functions once I have the database migrated into Postgres. Can someone please explain how to make use of them? In MySQL, the table exists: CREATE TABLE accessright ( acce

[ADMIN] how to handle larger databases?

2004-11-16 Thread matthias
I am currently creating a database which will have less than 20 quite simple tables. Unfortunately, some of those tables will have more than 1 million entries. In order to maintain fairly good query times I would like to ask for some tips on how I should organize that database, what I should do or

[ADMIN] Please help!!!!!!!!!

2004-11-16 Thread jagbirs
Hi, Im migrating our database from MSSQL7.0 to postgresql on Solaris 9(sparc).But we have got problem in compiling the source code of postgresql on solaris.Can we have precompiled package of postgresql stable version for solaris9 sparc plateform. Its urgent, please help us. Jagbir Singh "The C

[ADMIN] psql: FATAL: user "root" does not exist createdb: database creation failed

2004-11-16 Thread Jeoffrey L. Palacio
Hi to all I'm Jeoffrey, and I'm a newbie to postgreSQL. My problem is that when i execute the command createdb i always get a [EMAIL PROTECTED] root]# createdb ibmadb psql: FATAL: user "root" does not exist createdb: database creation failed Then I tried to create the user root by the comman

Re: [ADMIN] Please help!!!!!!!!!

2004-11-16 Thread Michael Fuhr
On Mon, Nov 15, 2004 at 10:15:30AM +0530, [EMAIL PROTECTED] wrote: > Hi, Im migrating our database from MSSQL7.0 to postgresql on > Solaris 9(sparc).But we have got problem in compiling the source > code of postgresql on solaris.Can we have precompiled package of > postgresql stable version for so

Re: [ADMIN] psql: FATAL: user "root" does not exist createdb:

2004-11-16 Thread Christian Fowler
execute these as the postgres user: su - postgres One option is to create a super-user with something like: postgres$ createuser -d -a -P jeoff then: jeoff$ createdb ibmadb then do administrative things with that user. I would advise *NOT* using root. If this is a tightly controlled (non-shared) m

[ADMIN] Websphere

2004-11-16 Thread Edoardo Ceccarelli
Hi, is there anybody that has successfully been able to configure postgresql with a ConnectionPoolDataSource under ibm websphere? What I really need is an opinion about it because I've been searching so much and it seems that neither on the websphere side, nor on the postgres one there is someth

[ADMIN] 7.3.4 -> 7.3.8 - a little stuck

2004-11-16 Thread ogjunk-pgjedan
Hello, I was using 7.3.4 and decided to upgrade to 7.3.8. I did this via RPMs for RH9. RPM installed OK, and the migration of data looks like it worked. I have one remaining problem: I can start the DB with `pg_ctl -D /var/lib/pgsql/data start', but I cannot start it with `/etc/rc.d/init.d/pos

Re: [ADMIN] 7.3.4 -> 7.3.8 - a little stuck

2004-11-16 Thread Tom Lane
<[EMAIL PROTECTED]> writes: > Although I upgraded to 7.3.8, I saw several incorrect(?) references to > 7.4 (e.g. PGVERSION=7.4 in that init script). Mistakes? Yes ... yours. You may have thought you updated to 7.3.8, but you evidently installed 7.4.something. regards, to