Re: [BUGS] Bug #612: PostgreSQL 7.2 does not build according to documentation under IRIX w/ MIPSpro
"Jonathan C. Patschke" <[EMAIL PROTECTED]> writes: > There's one warning that really bothered me, though. I don't know the > code well-enough to make this call, but I almost have to agree with the > compiler: Hmm ... it's correct, but my is it ugly. Someone trying to be too cute. Will change it to be more intelligible. 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
Re: [BUGS] Bug #612: PostgreSQL 7.2 does not build according to
> Ignore my submission about sh-vs-bash in configure. Configure is > still broken (doesn't set HAVE_SNPRINTF_DECL properly), and the > resulting tree still doesn't build under IRIX with MIPSpro ($CC > accidentally got reset to gcc between tries). Shows us the config.log file. -- Peter Eisentraut [EMAIL PROTECTED] ---(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
Re: [BUGS] Bug #621: why postgreSQL stored databases in
The numbers you see are OID'S, ie the OID of the relation. this is done to prevent name clashing and also makes fo easy lookups by the backend it self. At 12:18 PM 3/16/02 -0500, you wrote: >daizhong ([EMAIL PROTECTED]) reports a bug with a severity of 2 >The lower the number the more severe it is. > >Short Description >why postgreSQL stored databases in digital filenames? > >Long Description >In Mysql, database files as tables is stored in alpa. filename, >but why not postgresql uses digital filename? > >Sample Code > > >No file was uploaded with this report > > >---(end of broadcast)--- >TIP 6: Have you searched our list archives? > >http://archives.postgresql.org > > ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Bug #622: jdbc driver exception: failed to get datetime field from a table
Zhou Hui Qing ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
jdbc driver exception: failed to get datetime field from a table
Long Description
platform: SuSE 7.3 , Win2000 Server + cygwin !
When I using the example 'psql' (java example.psql jdbc:postgresql:mydb postgres
postgres) to retrive data from the table 'test' (select * from test) , I got an
exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: 23
java.lang.StringIndexOutOfBoundsException: String index out of range: 23
at java.lang.String.charAt(String.java:455)
at org.postgresql.jdbc2.ResultSet.toTimestamp(ResultSet.java:1653)
at org.postgresql.jdbc2.ResultSet.getTimestamp(ResultSet.java:398)
at org.postgresql.jdbc2.ResultSet.getObject(ResultSet.java:768)
at example.psql.displayResult(psql.java:137)
at example.psql.processLine(psql.java:96)
at example.psql.(psql.java:62)
at example.psql.main(psql.java:227)
Sample Code
java example.psql jdbc:postgresql:mydb postgres postgres
create table test(id serial primary key , name varchar(20) , dt datetime default now()
);
insert into test (name) values ('my name');
select * from test;
--got an error!
No file was uploaded with this report
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] psql's \r does not reset parenthesis depth counter
Tom Lane wrote: > In current sources: > > regression=# create table tt1 (i2 int2, i4 int4, f8 float8, > regression(# \r > Query buffer reset (cleared). > regression(# select 2; > regression(# -- nothing happens because psql still wants a right paren > > Not sure if there is any other state that needs to be reset along > with the paren counter. Are you sure you are running current? test=> create table tt1 (i2 int2, i4 int4, f8 float8, test(> \r Query buffer reset (cleared). test=> select 2; ?column? -- 2 (1 row) This was fixed in my post 7.2 patch. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] referential constraint bug
Patch applied. Thanks.
---
Stephan Szabo wrote:
>
> On Wed, 6 Mar 2002, Eric Lu wrote:
>
> > To whom it may concern:
> >
> > I found a constraint bug on PostgreSQL lastest version (7.2).
>
> Yes, it's still seeing some invalid states of the table. I believe
> the following will fix the case (it was part of a larger patch that
> was rejected, but I think this part is safe -- if not I'm sure someone
> will jump in).
>
> *** pgsql/src/backend/utils/adt/ri_triggers.c.origTue Mar 12 23:33:32 2002
> --- pgsql/src/backend/utils/adt/ri_triggers.c Tue Mar 12 23:33:47 2002
> ***
> *** 208,213
> --- 208,224
> new_row = trigdata->tg_trigtuple;
> }
>
> + /*
> + * We should not even consider checking the row if it is no longer
> + * valid since it was either deleted (doesn't matter) or updated
> + * (in which case it'll be checked with its final values).
> + */
> + if (new_row) {
> + if (!HeapTupleSatisfiesItself(new_row->t_data)) {
> + return PointerGetDatum(NULL);
> + }
> + }
> +
> /* --
>* SQL3 11.9
>* Gereral rules 2) a):
>
>
>
> ---(end of broadcast)---
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup.| Drexel Hill, Pennsylvania 19026
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
