[BUGS] Bug #711: Automatic created indexes can in some cases not be referenced to

2002-07-12 Thread pgsql-bugs
Lasse L. Johnsen ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description Automatic created indexes can in some cases not be referenced to Long Description It looks as if automatic created indexes can in some cases not be referenced to

Re: [BUGS] Bug #711: Automatic created indexes can in some cases not be referenced to

2002-07-12 Thread Hugo Jonker
On Fri, Jul 12, 2002 at 07:19:58AM -0400, [EMAIL PROTECTED] wrote: > Long Description > It looks as if automatic created indexes can in some cases not be referenced to >because long names are truncated. See example SQL statement below. There's a typo in your statement. The sequence name gets tr

Re: [BUGS] pg_dumpall forces plain text format

2002-07-12 Thread Andrew Kohlsmith
> > Is there a particular reason why plain text is forced? > Because pg_dumpall is producing a script file. > This is obviously not optimal, but it's not very clear how to do better. Agreed. :-) I notice that pg_dumpall just uses a query to grab a list of databases and some information about t

Re: [BUGS] pg_dumpall forces plain text format

2002-07-12 Thread Andrew Kohlsmith
> > Or is that on the TODO for whenever foreign keys can be across databases? > I very seriously doubt that PG will *ever* support foreign keys across > databases. No problem. I'm not that advanced of a user or admin to want it, I was just trying to peer into the crystal ball and try to anticip

Re: [BUGS] 7.2.1 backend crash (convert_string_datum, locale)

2002-07-12 Thread Andrew Sullivan
On Thu, Jul 11, 2002 at 11:15:42PM -0400, Tom Lane wrote: > Mats Lofkvist <[EMAIL PROTECTED]> writes: > > When testing postgres 7.2.1 on a sparc/solaris8 box with > > --enable-locale --enable-multibyte I get a crash in > > convert_string_datum. > > This smells like a problem that we chased down a

[BUGS] postgres.h MACRO issues

2002-07-12 Thread David Busby
Elephant Developers, I've got a bit of an issue with using your macros while building my own C function for PostgreSQL (btw: C functions are a wa cool feature). So I'm returning a char(32) from my function and I'm using the text* structure to work with my data. Here's where I've g

[BUGS] problem with query in postgres 6.5

2002-07-12 Thread praveen vejandla
Hi, I was able to run the below query successfully on PostgreSQL 7.0. SELECT substring(now() from 1 for 10); How ever if I run the same query on PostgreSQL 6.5, I am getting the below error. No such function 'substr' with the specified attributes. Can you pls let me know if there is any sol

[BUGS] getting only date

2002-07-12 Thread praveen vejandla
Hi all, is there any way to get only date in -MM-DD format from a Timestamp column in potsgresql 6.5 Thanks and regards, praveen _ There is always a better job for you at Monsterindia.com. Go now http://monsterindia.rediff.com/jobs -

Re: [BUGS] Bug #711: Automatic created indexes can in some cases not be referenced to

2002-07-12 Thread Tom Lane
[EMAIL PROTECTED] writes: > # CREATE TABLE WHOIS_BLOCK_TABLE_DATE ( > # BLOCK SERIAL UNIQUE, > # CREATE INT,-- Timestamp > # UPDATE INT -- Timestamp > # ); > NOTICE: CREATE TABLE will create implicit sequence >'whois

Re: [BUGS] postgres.h MACRO issues

2002-07-12 Thread Tom Lane
David Busby <[EMAIL PROTECTED]> writes: > // Put my 32 bytes into the buffer, this works perfect > memcpy(VARDATA(out_text), pbuf, 32); > // Tell it the buffer size > // I don't like that I've got to add the header size myself > // could/should VARATT_SIZEP handle that for me? > VARATT_SIZEP(out_t

Re: [BUGS] problem with query in postgres 6.5

2002-07-12 Thread Tom Lane
"praveen vejandla" <[EMAIL PROTECTED]> writes: > Can you pls let me know if there is any solution for this. Update your 6.5 installation. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once

[BUGS] It is a bug in pred_test()! (Was: [SQL] Please, HELP! Why is the query plan so wrong???)

2002-07-12 Thread Dmitry Tkach
Jie Liang wrote: >please copy and paste the whole msg and your query! >Note:what I mean ' join key' is the fields that link two tables. > The message (query plan) is exactly the same (you can see it in the bottom of this message). > >I don't think fb.b=0 is a join key! > Of course not. But it I

Re: [BUGS] pg_dumpall forces plain text format

2002-07-12 Thread Bruce Momjian
Andrew Kohlsmith wrote: > > > Is there a particular reason why plain text is forced? > > Because pg_dumpall is producing a script file. > > This is obviously not optimal, but it's not very clear how to do better. > > Agreed. :-) > > I notice that pg_dumpall just uses a query to grab a list of d