Re: [HACKERS] [SQL] Case Preservation disregarding case

2006-11-06 Thread Martijn van Oosterhout
to clients to make PQfname work, and that's going to messy. Have a nice day, -- Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to > litigate. signature.asc Description: Digital signature

Re: [GENERAL] [SQL] index row size 2728 exceeds btree maximum, 2713

2005-06-05 Thread Martijn van Oosterhout
> > Indexes: > > "pk_scanned_port_info" PRIMARY KEY, btree (scan_id, host_ip, port_num, > plugin_id, severity, data) > > > > > > On inserting record I am getting this error "index row size 2728 exceeds > btree maximum, 2713" >

Re: [SQL] [GENERAL] Get current trasanction id

2004-12-30 Thread Martijn van Oosterhout
ql ? > > Thanks in advance for any help. > > ML > > > > ---(end of broadcast)--- > TIP 2: you can get off all lists at once with the unregister command >(send "unregister YourEmailAddressHere" to

Re: [SQL] [GENERAL] Postgresql slow on XEON 2.4ghz/1gb ram

2003-08-14 Thread Martijn van Oosterhout
al and shmem option appropriate for that size machine. But in any case, without specific examples about what you're seeing we can't help you. -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > "All that is needed for the forces of evil to triumph

Re: [SQL] [GENERAL] CURRENT_TIMESTAMP

2002-10-04 Thread Martijn van Oosterhout
e 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 > > -

Re: [SQL] [GENERAL] CURRENT_TIMESTAMP

2002-10-04 Thread Martijn van Oosterhout
On Sat, Sep 28, 2002 at 11:51:32PM -0400, Bruce Momjian wrote: > Martijn van Oosterhout wrote: > > Well, I'd rather it didn't change at all. IMHO it's a feature, not a bug. In > > any case, if it does get changed we'll have to go through the documentati

Re: [SQL] [GENERAL] CURRENT_TIMESTAMP

2002-09-27 Thread Martijn van Oosterhout
add a todo and make clear in the documentation that > CURRENT_DATE/TIME/TIMESTAMP is not SQL92/99 compliant. The current definition is, I would say, the most useful definition. Can you give an example where your definition would be more useful? -- Martijn van Oosterhout <[EMAIL PROTECTED]&g

Re: [SQL] [GENERAL] id and ID in CREATE TABLE

2002-07-19 Thread Martijn van Oosterhout
ly will your program work, it's will be completely portable. So, if you'd used your CREATE TABLE statememnt below, you wouldn't have had this problem. > > CREATE TABLE ttt ( > > > > ID int2, > > name text ); -- Martijn van Oosterhout <[EMAIL PR

[SQL] Re: [GENERAL] Query Approach and performance

2001-08-20 Thread Martijn van Oosterhout
o through the compile phase and run faster? Is this configurable? Hmm, I've never noticed that query compilation actually took any noticable time. No, postgres doesn't do that but I'm not convinced it would make a difference. HTH, -- Martijn van Oosterhout <[EMAIL PROTECTED]>

Re: [GENERAL] two tables - foreign keys referring to each other...

2001-02-20 Thread Martijn van Oosterhout
On Wed, Feb 21, 2001 at 12:30:51PM +0900, Chris Czeyka wrote: [big snip] > of course I get the ERROR, that admin_t doesn't exist. So? help the stupid! > pls! I think the general idea is to create the tables first without the constraints and then do ALTER TABLE ADD CONSTRAINT afterwards. HTH,