[BUGS] problems_with_installation
Hallo everybody, I have problem with postgresInstalation 7.2b5 The problems occurs when I try to create a dbcluster. When I write initdb everything seeds to be OK but there is an error: creating configuration files... ok initializing pg_shadow... initdb failed. This is the full information: initdb -E LATIN2 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. Fixing permissions on existing directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok creating template1 database in /usr/local/pgsql/data/base/1... ok creating configuration files... ok initializing pg_shadow... initdb failed. I compiled postgres with multibyte support LATIN2. Please help, Daniel ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] problems_with_installation
[EMAIL PROTECTED] writes: > I have problem with postgresInstalation 7.2b5 Why in the world are you still using a beta version? Get 7.2.2. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] UNICODE lower/upper problems
Hi, I have a problem with lower/upper functions. It seems that the lower function modifies some of the unicode characters(german, hungarian, romanian) and the upper case function modifies other(hindi). When i say modifies i don't mean it transforms the the character in it's lower/upper form. It simply transforms some of the characters into mush(the charaters are distorted or transformed to "") To test this i used one special character on each record and used "SELECT x, LOWER(x), UPPER(x) FROM test_unicode" Anyhow... i attached the dump so you can test it yourself. What do you think is the problem? Thanks, xayk
[BUGS] UNICODE lower/upper problems
I have a problem with lower/upper functions. It seems that the lower function modifies some of the unicode characters(german, hungarian, romanian) and the upper case function modifies other(hindi). When i say modifies i don't mean it transforms the the character in it's lower/upper form. It simply transforms some of the characters into mush(the charaters are distorted or transformed to "") To test this i used one special character on each record and used "SELECT x, LOWER(x), UPPER(x) FROM test_unicode" Anyhow... i attached the dump so you can test it yourself. What do you think is the problem? Thanks, xayk AI_UNICODE.dump Description: Binary data ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] c.h needed in Pg.c
On Mon, Aug 26, 2002 at 00:34:00 -0400, Tom Lane <[EMAIL PROTECTED]> wrote: > Bruno Wolff III <[EMAIL PROTECTED]> writes: > > When trying to build from CVS, interfaces/perl5 doesn't build unless I add > > an include of "c.h" in Pg.c. > > Works fine here --- and I'm not inclined to include a backend include > file into a frontend module if it can possibly be avoided. Please be > more specific about what failure you're seeing, and on what platform. > > regards, tom lane I sent make output and a config log here (and maybe copied Tom Lane) for this issue. But I think I might have hit a size limit with the message as it hasn't shown up yet. Is there someplace else I should send the information? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] Bug #751: LASTOID in 7.2.1 with INSERT RULES ON VIEWS
Toni Garcia ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
LASTOID in 7.2.1 with INSERT RULES ON VIEWS
Long Description
This fix on 7.2.1 has apparently changed the OID that is returned
with ON INSERT rules:
- Return proper OID on command completion even with ON INSERT rules (Tom)
The 7.2.1 behaivour (returning the OID generated by the first command) is good for
rules ON INSERT on tables with
no DO INSTEAD command but i think it makes no sense for view rules or DO INSTEAD rules
where there is no OID for the first command.
Sample Code
CREATE table myobject (
name varchar(32) PRIMARY KEY,
aproperty varchar(32),
anotherproperty varchar(32)
);
CREATE table myimage (
name varchar(32) PRIMARY KEY,
image oid,
CONSTRAINT FK_obj_ima_1 FOREIGN KEY (name) REFERENCES myobject(name) ON UPDATE
CASCADE ON DELETE CASCADE
);
CREATE VIEW myimage_obj AS
select i.oid, i.*, o.aproperty, o.anotherproperty from myimage i, myobject o where
i.name = o.name;
CREATE RULE myimage_ins AS
ON INSERT TO myimage_obj
DO INSTEAD
(
INSERT into myobject
(name, aproperty, anotherproperty)
values (NEW.name, NEW.aproperty, NEW.anotherproperty);
INSERT into myimage
(name, image)
values (NEW.name, NEW.image);
);
this used to return myimage's oid (last inserted oid) on 7.2.0:
=# INSERT INTO myimage_obj (name, aproperty) values ('mygif', 'verybig');
INSERT 0 0
No file was uploaded with this report
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] cube bug accepting -.1
Patch withdrawn by author. --- Bruno Wolff III wrote: > The lex scanner for the cube package has an apparent error in its > pattern for matching floating point numbers. It doesn't except cases > where there is no digit between a sign and a decimal point. For example > -.1 is not matched by the pattern. > > I have attached a patch to cubeparse.l and the regression differences. > > P.S. I still plan to submit enhancement patches for cube before the > end of the week, but as this is a bug fix I thought it should really > go in separately. [ Attachment, skipping... ] [ Attachment, skipping... ] > > ---(end of broadcast)--- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] Bug #752: I fixed (worked arround) bug pqReadData function on HPUX
Diedrich Vorberg ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description I fixed (worked arround) bug pqReadData function on HPUX Long Description Version: 7.2.1 uname -a: HP-UX c200 B.11.11 U 9000/782 I used to get a "could not receive data from server: Error: 0" error message from the pqReadData function in fe-misc.c:491. Turns out recv() returnes -1 but set errno to 0. I just guessed that means there´s nothing more to read and added a line if (SOCK_ERRNO == 0) return someread; which made the problem go away. I have not taken the time to investigate further and I am afraid my expertise is insufficient :) Sorry about my poor Server-programming, hope this points you in the right direction. Diedrich Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
