Re: [HACKERS] Posix AIO in new Red Hat Linux

2002-03-30 Thread Greg Copeland
Cool. Thanks for the information. The only other PAIO effort that I knew of was the glibc user space effort... Greg On Sat, 2002-03-30 at 12:36, Neil Conway wrote: > On Sat, Mar 30, 2002 at 09:59:11AM -0600, Greg Copeland wrote: > > It doesn't really say, however, it makes me

Re: [HACKERS] Posix AIO in new Red Hat Linux

2002-03-30 Thread Greg Copeland
It doesn't really say, however, it makes me wonder if it's SGI's KAIO (http://oss.sgi.com/projects/kaio/) effort which is reported to provide up to 35% performance improvement for heavily I/O bound applications. Again, I'm not sure it is SGI's effort that is being talked about here, nonetheless,

Re: [HACKERS] notification: pg_notify ?

2002-03-23 Thread Greg Copeland
What if we used a combination of the two approaches? That is, when an overflow occurs, overflow into a table? That way, nothing is lost and spurious random events don't have to occur. That way, things are faster when overflows are not occurring. When the system gets too far behind, it simply o

Re: Fw: Fw: [HACKERS] bad performance on irix

2002-03-22 Thread Greg Copeland
On a side note, I thought I would mention that the Next Generation POSIX Threading (NGPT) Project (IBM -- http://www-124.ibm.com/developerworks/projects/pthreads) patches have just been accepted to the 2.5.x Linux kernel. A 2.4.x patch is also available. So, it may be possible that POSIX mutexes

Re: [HACKERS] Function call crashes server

2002-03-20 Thread Greg Copeland
Does the same thing here. Sounds like a serious problem to me too. Greg On Wed, 2002-03-20 at 20:46, Bruce Momjian wrote: > If I do this as any user: > > SELECT update_pg_pwd(); > > it crashes all backends and causes a server-wide restart. Is this > acceptable behavior? I am sure ther

Re: [HACKERS] Bitmap indexes?

2002-03-19 Thread Greg Copeland
On Tue, 2002-03-19 at 15:30, Matthew Kirkwood wrote: > On Tue, 19 Mar 2002, Oleg Bartunov wrote: > > Sorry to reply over you, Oleg. > > > On 13 Mar 2002, Greg Copeland wrote: > > > > > One of the reasons why I originally stated following the hackers list is &g

Re: [HACKERS] Again, sorry, caching, (Tom What do you think: function

2002-03-19 Thread Greg Copeland
On Tue, 2002-03-19 at 07:46, mlw wrote: > I was thinking about this. There seems to be a consensus that caching means no > ACID compliance. And everyone seems to think it needs to be limited. We can > implement a non-ACID cache as a contrib function with some work to the function > manager. Until

Re: [HACKERS] Again, sorry, caching, (Tom What do you think: function

2002-03-19 Thread Greg Copeland
On Tue, 2002-03-19 at 07:46, mlw wrote: [snip] > Right now, the function manager can only return one value, or one set of values > for a column. It should be possible, but require a lot of research, to enable > the function manager to return a set of rows. If we could get that working, it > could

Re: [HACKERS] Again, sorry, caching.

2002-03-19 Thread Greg Copeland
On a side note, is it possible that we could add the "iscachable" which for now, would give cache bias? That is, allow for a mechanism to indicate that the pages that are required for this query will be frequently needed. I've not looked at the buffer cache implementation. Is it possible to som

Re: [HACKERS] Again, sorry, caching.

2002-03-18 Thread Greg Copeland
On Mon, 2002-03-18 at 20:35, Neil Conway wrote: [snip] > My impression (I could be wrong) is that LISTEN/NOTIFY doesn't get the > press that it deserves. If this model isn't widely used because of some > deficiencies in the LISTEN/NOTIFY implementation, IMHO our time would be > better spent fixi

Re: [HACKERS] Again, sorry, caching.

2002-03-18 Thread Greg Copeland
On Mon, 2002-03-18 at 10:08, mlw wrote: > Greg Copeland wrote: > > > > On Mon, 2002-03-18 at 08:15, mlw wrote: > > > "Mattew T. O'Connor" wrote: > > > > [snip] > > > > If you are using a web site and you need real time data with

Re: [HACKERS] Again, sorry, caching.

2002-03-18 Thread Greg Copeland
On Mon, 2002-03-18 at 08:15, mlw wrote: > "Mattew T. O'Connor" wrote: > > [snip] > > >The primary use that you have suggested is for web sites, > > and they certainly won't mind of the cache is 0.3seconds out of date. > > Again, if they don't care about accuracy, then they will use MySQL. Post

Re: [HACKERS] Again, sorry, caching.

2002-03-18 Thread Greg Copeland
Yes. EVERY person that I've ever known which runs MySQL run for two very simple reasons. First, they believe it to be wicked fast. Second, they don't understand what ACID is, what a transaction is, or why running a single session against a database to perform a benchmark is a completely bogus c

Re: [HACKERS] Client/Server compression?

2002-03-16 Thread Greg Copeland
Some questions for you at the end of this Tom...which I'd been thinking about...and you touched on...hey, you did tell me to ask! :) On Sat, 2002-03-16 at 14:38, Tom Lane wrote: > Greg Copeland <[EMAIL PROTECTED]> writes: > > I'm talking about something that would be

Re: [HACKERS] Again, sorry, caching.

2002-03-16 Thread Greg Copeland
On Sat, 2002-03-16 at 08:36, mlw wrote: > Triggers and asynchronous notification are not substitutes for real hard ACID > complient caching. The way you suggest implies only one access model. Take the > notion of a library, they have both web and application access. These should > both be able to

Re: [HACKERS] Again, sorry, caching.

2002-03-16 Thread Greg Copeland
On Sat, 2002-03-16 at 08:01, mlw wrote: [snip] > "If it is mostly static data, why not just make it a static page?" > Because a static page is a maintenance nightmare. One uses a database in a web > site to allow content to be changed and upgraded dynamically and with a minimum > of work. > Oh

Re: [HACKERS] Again, sorry, caching.

2002-03-16 Thread Greg Copeland
I previously replied to you vaguely describing a way you could implement this by using a combination of client side caching and database tables and triggers to allow you to determine if your cache is still valid. Someone came right behind me, Tom maybe??, and indicated that the proper/ideal way t

Re: [HACKERS] User Level Lock question

2002-03-15 Thread Greg Copeland
On Fri, 2002-03-15 at 21:45, Lance Ellinghaus wrote: > The application actually does not want nor need a consistent view of the > data. It is expecting that records that are locked will not be viewed at > all. The locks are normally held for VERY short periods of time. The fact > that the applicat

Re: [HACKERS] Client/Server compression?

2002-03-15 Thread Greg Copeland
On Fri, 2002-03-15 at 19:44, Kyle wrote: [snip] > Wouldn't Tom's suggestion of riding on top of ssh would give similar > results? Anyway, it'd probably be a good proof of concept of whether > or not it's worth the effort. And that brings up the question: how > would you measure the benefit? I'

Re: [HACKERS] User Level Lock question

2002-03-15 Thread Greg Copeland
On Fri, 2002-03-15 at 16:24, Neil Conway wrote: > On Fri, 2002-03-15 at 14:54, Lance Ellinghaus wrote: > > I know it does not sound like something that would need to be done, but here > > is why I am looking at doing this... > > > > I am trying to replace a low level ISAM database with PostgreSQL

Re: [HACKERS] User Level Lock question

2002-03-15 Thread Greg Copeland
Are you trying to do a select for update? Greg On Fri, 2002-03-15 at 13:54, Lance Ellinghaus wrote: > I know it does not sound like something that would need to be done, but here > is why I am looking at doing this... > > I am trying to replace a low level ISAM database with PostgreSQL. The lo

Re: [HACKERS] Client/Server compression?

2002-03-15 Thread Greg Copeland
On Thu, 2002-03-14 at 19:43, Bruce Momjian wrote: > Kyle wrote: > > On the subject on client/server compression, does the server > > decompress toast data before sending it to the client? Is so, why > > (other than requiring modifications to the protocol)? > > > > On the flip side, does/could th

Re: [HACKERS] Client/Server compression?

2002-03-15 Thread Greg Copeland
On Thu, 2002-03-14 at 14:03, Arguile wrote: [snip] > I'm sceptical of the benefit such compressions would provide in this setting > though. We're dealing with sets that would have to be compressed every time > (no caching) which might be a bit expensive on a database server. Having it > as a def

Re: [HACKERS] Client/Server compression?

2002-03-14 Thread Greg Copeland
On Thu, 2002-03-14 at 14:29, Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > >> This may be of value for users with low bandwidth connectivity to their > >> servers or where bandwidth may already be at a premium. > > > But don't slow links do the compression themselves, like PPP ove

Re: [HACKERS] Client/Server compression?

2002-03-14 Thread Greg Copeland
On Thu, 2002-03-14 at 14:14, Neil Conway wrote: > On Thu, 2002-03-14 at 14:35, Bruce Momjian wrote: > > Greg Copeland wrote: > > > > Checking application/pgp-signature: FAILURE > > -- Start of PGP signed section. > > > Well, it occurred to me that if a la

Re: [HACKERS] Client/Server compression?

2002-03-14 Thread Greg Copeland
On Thu, 2002-03-14 at 13:35, Bruce Momjian wrote: > Greg Copeland wrote: > > Checking application/pgp-signature: FAILURE > -- Start of PGP signed section. > > Well, it occurred to me that if a large result set were to be identified > > before transport between a client a

Re: [HACKERS] Client/Server compression?

2002-03-14 Thread Greg Copeland
with low bandwidth connectivity to their servers or where bandwidth may already be at a premium. The zlib exploit posting got me thinking about this. Greg On Thu, 2002-03-14 at 12:20, Bruce Momjian wrote: > Greg Copeland wrote: > > Just curious, and honestly I haven't looked, bu

[HACKERS] Client/Server compression?

2002-03-14 Thread Greg Copeland
Just curious, and honestly I haven't looked, but is there any form of compression between clients and servers? Has this been looked at? Greg signature.asc Description: This is a digitally signed message part

<    1   2   3