[BUGS] BUG #1102: DOMAIN definition too late in pg_dump

2004-03-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1102
Logged by:  klaus daum

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   linux 2.4

Description:DOMAIN definition too late in pg_dump

Details: 

using pg 7.4.2:

- create table t
- insert data into table t
- create domain d
- add col to table t with domain d
- pg_dump output has: definition of domain d after defintion of table t (not 
readable without edit of dump) 

regards,
klaus


---(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 #1103: automatic no generartion

2004-03-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1103
Logged by:  nagendra kumar

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.5 Dev

Operating system:   windows

Description:automatic no generartion

Details: 

  i want automatic genarating of an application no using a quary   


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [BUGS] BUG #1102: DOMAIN definition too late in pg_dump

2004-03-17 Thread Tom Lane
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:DOMAIN definition too late in pg_dump

pg_dump ordering is a longstanding problem.  It's fixed in CVS tip,
I believe, but the changes were too major to consider back-patching.

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html


[BUGS] BUG #1104: postmaster crashes

2004-03-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1104
Logged by:  Neeraj K Sharma

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux 7.3 Kernel 2.4.19

Description:postmaster crashes

Details: 

Hi Tom,

I have already filed this bug. I have been also asked more information. I 
was trying to reply your mail but event time it was bounced with the 
following message. 


[***] 
[BUGS] BUG #1074: postgresql crashes 

This is the Postfix program at host cmlapp00.siteprotect.com.

I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.

For further assistance, please send mail to 

If you do so, please include this problem report. You can delete your own 
text from the message returned below. 

The Postfix program

<[EMAIL PROTECTED]>: host sss.pgh.pa.us[192.204.191.242] said: 550 5.0.0 Go
away, spammer (in reply to MAIL FROM command)


Reporting-MTA: dns; cmlapp00.siteprotect.com
Arrival-Date: Wed, 18 Feb 2004 19:32:59 -0600 (CST)

Final-Recipient: rfc822; [EMAIL PROTECTED]
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host sss.pgh.pa.us[192.204.191.242] said: 550 
5.0.0 
Go away, spammer (in reply to MAIL FROM command)]

--- Tom Lane <[EMAIL PROTECTED]> wrote:

> "PostgreSQL Bugs List" <[EMAIL PROTECTED]>

> writes:

> > The database cores with the following message

> printed on screen.

> > WARNING:  specified item offset is too large

> 

> Hmm.  AFAICS this should always be followed by an

> ERROR message.  There

> are at least two issues here: why does this message

> occur, and why does

> a crash follow instead of more-graceful error

> recovery?

> 

> Does any additional information show up in the

> postmaster log?

> 

> Could you provide your test program?  Could you

> provide a stack trace

> from the backend core dump?

> 

>  regards, tom lane]

**

Here I am sending you now logfile, code stack trace, & code dump file.

I was trying to create a small program that could simulate out system but so 
far that program is not able to reproduce the bug. I might have to make more 
changes in the program. I'll let you know as soon as I have that program 
ready. 

* logfile ***
WARNING:  specified item offset is too large
PANIC:  failed to add item to the page for "s_stream_status_change_idx"
STATEMENT:  INSERT INTO S_STREAM_STATUS_CHANGE VALUES 
('1376578','TestStream:1079033994852:27:1378591','f','0','0') 
LOG:  server process (PID 27467) was terminated by signal 6
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and 
 possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat your command. 
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and 
 possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat your command. 
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and 
 possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat your command. 
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the 
current transaction and exit, because another server process exited 
abnormally and 
 possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and 
repeat your command. 
WARNING:  terminating connection because of crash of another server process
***

** CORE STACK TRACE ***
(gdb) where
#0  0x42029241 in kill () from /lib/i686/libc.so.6
#1  0x4202902a in raise () from /lib/i686/libc.so.6
#2  0x4202a7d2 in abort () from /lib/i686/libc.so.6
#3  0x081bac1d in errfinish ()
#4  0x081bb6bf in elog_finish ()
#5  0x08083781 in _bt_pgaddtup ()
#6  0x08082378 in _bt_insertonpg ()
#7  0x08083211 in _bt_insert_parent ()
#8  0x080822a1 in _bt_insertonpg ()
#9  0x08081beb in _bt_doinsert ()
#10 0x0808544a in btinsert ()
#11 0x081bee7b in OidFunctionCall6 ()
#12 0x08081162 in index_insert ()
#13 0x080f8d29 in ExecI

[BUGS] BUG #1105: psotmaster error

2004-03-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1105
Logged by:  bujji babu

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   windows2000

Description:psotmaster error

Details: 

$ postmaster -D /usr/share/postgresql/data -h localhost -i -N 10  -s -p 777 
& 
[3] 1776

[EMAIL PROTECTED] ~
$ LOG:  could not connect socket for statistics collector: Connection 
refused 
LOG:  disabling statistics collector for lack of working socket
LOG:  database system was interrupted at 2004-03-18 09:36:28 IST
LOG:  checkpoint record is at 0/9DEB48
LOG:  redo record is at 0/9DEB48; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 534; next OID: 17142
LOG:  database system was not properly shut down; automatic recovery in 
progress 
LOG:  record with zero length at 0/9DEB88
LOG:  redo is not required
LOG:  database system is ready


when i am giving this i get this eror, please send reply 


---(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] BUG #1106: Big5 String equal doesn't work

2004-03-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1106
Logged by:  Jer-Min Tsai

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 7.4

Operating system:   Linux Fedora Core 1

Description:Big5 String equal doesn't work

Details: 

DataBase Version 7.4 ,7.2
DataBase Encoding EUC_TW
client encoding Big5

SQL as below:

create table main(
name character(10),
gender character(1),  
birthday timestamp,
tel character(16), 
fax character(16),
mobil character(16),
email character(60),
address character(100)
);


insert into main values 
('蔡哲民','男','1986/02/13','07-1234567','06-03213213','09311234567' 
,'[EMAIL PROTECTED]','台南市南區北門路');
insert into main values 
('陳水扁','男','1943/05/15','06-1234567','02-03213213','09181234567' 
,'[EMAIL PROTECTED]','台南縣官田鄉官田路');
insert into main values 
('連戰','男','1923/06/16','02-7654321','02-43210321','09601234567' 
,'[EMAIL PROTECTED]','台北市天母');
insert into main values 
('宋楚瑜','男','1928/02/18','04-1234567','04-03213213','09601234567' 
,'[EMAIL PROTECTED]','台北市總統路');
insert into main values 
('吳淑珍','女','1943/02/13','06-1234567','02-03213213','09181234567' 
,'[EMAIL PROTECTED]','台南縣官田鄉官田路');
insert into main values 
('呂秀蓮','女','1935/12/05','02-1234567','02-03213213','09184321231' 
,'[EMAIL PROTECTED]','桃園縣桃園市總統路');

select * from main where gender='男';


It can not show only gender='男'.
I tried Like '男' is ok. = ASCII String is ok.



---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings