[BUGS] Wrong formated date on the first day of the Daylight Saving time.
Laurent Faillie ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Wrong formated date on the first day of the Daylight Saving time. Long Description Hi every body, I find this problem using the following configuration: $ uname -a HP-UX arvipa B.10.20 A 9000/715 2003042439 two-user license $ gcc -v gcc version 2.95.2 19991024 (release) PostGreSQL v 7.0.3 I use PostGreSQL to store some statistics. The weekend we switch from normal time (TZ=MET-1MET) to daylight saving time (TZ=MET-1METDST), and when i read statistics from this W.E., I saw a dupplicate data. In fact the problem was only on the display. Please see the code bellow. As you can see, 24 Mar 2001 is displayed twice. Bye Laurent Sample Code scheduling=# select to_char( jour, 'DayDD Mon '), jour from backlog where jour>'2001-03-23'; to_char |jour -+ Saturday 24 Mar 2001 | 2001-03-24 Saturday 24 Mar 2001 | 2001-03-25 Monday 26 Mar 2001 | 2001-03-26 Tuesday 27 Mar 2001 | 2001-03-27 (4 rows) No file was uploaded with this report ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Wrong formated date on the first day of the Daylight Saving time.
On Tue, Mar 27, 2001 at 04:35:11AM -0500, [EMAIL PROTECTED] wrote: > Short Description > Wrong formated date on the first day of the Daylight Saving time. It's common problem with this time in 7.0.x - already fixed in 7.1. > scheduling=# select to_char( jour, 'DayDD Mon '), jour from >backlog where jour>'2001-03-23'; > to_char |jour > -+ > Saturday 24 Mar 2001 | 2001-03-24 > Saturday 24 Mar 2001 | 2001-03-25 > Monday 26 Mar 2001 | 2001-03-26 > Tuesday 27 Mar 2001 | 2001-03-27 > (4 rows) Note: use quotation marks for non-format masks, it is faster. En example: to_char( jour, '""Day""DD Mon ') Karel -- Karel Zak <[EMAIL PROTECTED]> http://home.zf.jcu.cz/~zakkr/ C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz PGP signature ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Please help On Alternative Database Location
it's sure that this email should to be write to anywhere but here, but the various requests to help done in some mailings lists about postgresqk are failed.So i write you, in the hope to receive an response. Briefly the question. I work under Linux platform, Mandrake 7.2 distribution, and i need to create a postgres database, for example called "mydb", in alternative location, for example "/home/username". In the official documentation this is very simple to do, but in the reality i have failed. This is my steps 1) su - username 2) set PGDATA2 = "/home/username" (but i tried relatives path too) 3) initlocation $PGDATA2 4) createdb -D $PGDATA2 mydb Finally an error message appears like this "The database path '/home/username' is invalid. This may be due to a character that is not allowed or because the chosen path isn't permitted for databases" I tried the relatives paths "~" and "." too, but the message is the same. Please help me I like to know the right procedure step by step Thanck you so much __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Please help On Alternative Database Location
Francesco Protano <[EMAIL PROTECTED]> writes: > I work under Linux platform, Mandrake 7.2 > distribution, and i need to create a postgres > database, for example called "mydb", in alternative > location, for example "/home/username". In the > official documentation this is very simple to do, but > in the reality i have failed. > This is my steps > 1) su - username > 2) set PGDATA2 = "/home/username" (but i tried > relatives path too) > 3) initlocation $PGDATA2 > 4) createdb -D $PGDATA2 mydb The environment variable PGDATA2 needs to be present in the postmaster's environment, not only the client's. Also, leave off the $ in steps 3 and 4; you are trying to pass the name of the environment variable to the postmaster, not its value. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Please help On Alternative Database Location
Francesco Protano writes: > 1) su - username > 2) set PGDATA2 = "/home/username" (but i tried > relatives path too) > 3) initlocation $PGDATA2 > 4) createdb -D $PGDATA2 mydb initlocation PGDATA2 createdb -D PGDATA2 mydb -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/ ---(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 about 'Foreign Key'
PostgreSQL Developers,
I have a PostgreSQL 7.0.2 running at Conectiva
Linux, with kernel 2.2.14, with 56 Mb of data.
I'd created a table:
Create Table Andamento (
Etiqueta integer not
null,
CodTecnico integer not
null,
DtInicio timestamp not
null,
DtLiberacao timestamp
null,
Primary Key
(Etiqueta),
Foreign Key (Etiquetas)
References Etiquetas (Etiqueta) On Delete Cascade)
I wrong a field name in Foreign Key declaration,
and PostgreSQL created it!
Before this, I always named triggers and
constraints, but, at this time, I'd tried this way.
Well, look the trigger at table
Etiquetas:
CREATE CONSTRAINT TRIGGER "" AFTER
DELETE ON "etiquetas" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('', 'andamento',
'etiquetas', 'UNSPECIFIED', 'etiquetas', 'etiqueta');
It says exists a field named etiquetas at table
Andamento.
I'd droped table andamento (Drop Table Andamento)
and the trigger referencing it didn't droped.
I solved it with
pg_dump.
Re: [BUGS] Local Host Security? All users should have passwordsoptionally...
> Iván Baldo ([EMAIL PROTECTED]) reports a bug with a severity of 2 > I wanted to add passwords to all the users on the database, including > the postgres user, etc. Then everything is authenticated using "crypt" > method, so it asks passwords EVERYTIME. The problem I found is that I > cannot do a "pg_dumpall" anymore, since I have no way to tell it to > use the "postgres" user with a given password. This is a known problem. You could try to patch pg_dumpall to pass the -u option every time it calls pg_dump and psql. > It tries to use the > user "root" without password and it fails miserably! What happens if a > hacker (or worst, a cracker!) enters to the machine somehow and I > don't ask passwords for unix domain sockets? Try changing the permissions on the socket file (chmod). -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/ ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Bug about 'Foreign Key'
This should be fixed for 7.1, it now checks that the
referencing columns exist on the fk table and that the
referenced columns are part of a unique index
[our unique/pkey] on the referenced table.
On Tue, 27 Mar 2001, Cid R Andrade wrote:
> PostgreSQL Developers,
>
> I have a PostgreSQL 7.0.2 running at Conectiva Linux, with kernel 2.2.14, with 56 Mb
>of data.
>
> I'd created a table:
> Create Table Andamento (
> Etiqueta integer not null,
> CodTecnico integer not null,
> DtInicio timestamp not null,
> DtLiberacao timestamp null,
> Primary Key (Etiqueta),
> Foreign Key (Etiquetas) References Etiquetas (Etiqueta) On Delete Cascade)
> I wrong a field name in Foreign Key declaration,
> and PostgreSQL created it! Before this, I always named triggers and
> constraints, but, at this time, I'd tried this way. Well, look the
> trigger at table Etiquetas: CREATE CONSTRAINT TRIGGER ""
> AFTER DELETE ON "etiquetas" NOT DEFERRABLE INITIALLY IMMEDIATE FOR
> EACH ROW EXECUTE PROCEDURE "RI_FKey_noaction_del" ('',
> 'andamento', 'etiquetas', 'UNSPECIFIED', 'etiquetas', 'etiqueta');
>
> It says exists a field named etiquetas at table Andamento.
> I'd droped table andamento (Drop Table Andamento) and the trigger referencing it
>didn't droped.
>
> I solved it with pg_dump.
>
---(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] pg v7.1RC1: jdbc1 fails to compile
Michael Fischer v. Mollard ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description pg v7.1RC1: jdbc1 fails to compile Long Description When I was compiling postgresql-7.1RC1 (on a debian 2.2 with a jdk118_v3 from blackdown.org) I got the following error: [javac] /home/mfvm/postgresql-7.1RC1/src/interfaces/jdbc/org/postgresql/jdbc1/Statement.java:291: Missing term. [javac] if (result != null) && ((org.postgresql.ResultSet)result.reallyResultSet()) [javac] ^ [javac] /home/mfvm/postgresql-7.1RC1/src/interfaces/jdbc/org/postgresql/jdbc1/Statement.java:291: Invalid expression statement. [javac] if (result != null) && ((org.postgresql.ResultSet)result.reallyResultSet()) [javac] ^ [javac] /home/mfvm/postgresql-7.1RC1/src/interfaces/jdbc/org/postgresql/jdbc1/Statement.java:291: ';' expected. [javac] if (result != null) && ((org.postgresql.ResultSet)result.reallyResultSet()) It seems as if this line does not contain valid java code. Simply using (result != null && ((org.postgresql.ResultSet)result).reallyResultSet()) which is a copy and paste from line 279, solves the compilation problem and seems to be the right thing. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
