Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?

1999-02-12 Thread Rudy Gireyev
Additionally manuals tend to be more of a reference whereas a book is primarily a tutorial, then at the end it can contain reference type material. If the book were to be written it would need complete and working examples followed by the exact result for example. Therefore I think it's a whole

RE: [GENERAL] limit select question

1999-03-31 Thread Rudy Gireyev
May be I'm missing something, but why not use the cursor? Do the select once and then fetch as many rows as you need. Rudy On 31 Mar 99, at 1:20, Michael Davis wrote: > Select * From table_name limit 1; > > -Original Message- > From:Kevin Heflin [SMTP:[EMAIL PROTECTED]] > Se

Re: [GENERAL] Performance

1999-03-31 Thread Rudy Gireyev
> > 1) All Celerons ship with a 128K on chip cache. Which means the cache > > runs at the same clock rate as the chip. 2) The PIIs ship with 512K > > cache, however it's level 2 so it only runs at bus speed. > > No, it runs at half the core speed. Oh shoot. You are absolutely right. I'm terribly

Re: [GENERAL] Two questions about join performance

1999-08-05 Thread Rudy Gireyev
Well maybe now is a good time to take a look at your design and see why you have to do this. There just happens to be a number of great DBAs on this list as well. :-) Rudy On 6 Aug 99, at 2:14, Roberto Moreda wrote: > Sorry for being so reiterative :) > > The planifier isn't perfect for many q

Re: [GENERAL] stored procedure revisited

1999-10-21 Thread Rudy Gireyev
On 12 Oct 99, at 19:34, Yin-So Chen wrote: [SP discussion snipped] > > Come on, everybody, speak out your thought on this matter :) Alright, alright. Last I used the SP was on a Teradata box, and I must admit it's a useful functionality. It makes the code much easier to read, in addition to all

Re: [GENERAL] Benchmarks (Vacuum)

2000-01-06 Thread Rudy Gireyev
While on the subject of vacuum. I wonder if Tom's time will be better utilized at figuring out how to get rid of vacuum all together rather than trying to fix it. Simply have that functionality replaced with a more modern way of data management and query optimization. That command was nothing but