Berkeley POSTGRES user mailing list (1991-06 → 1997-01)help / color / mirror / Atom feed
MIRO 5+ messages / 5 participants [nested] [flat]
* MIRO @ 1993-06-29 03:20 Chris Bunting 61-89-895442 <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Chris Bunting 61-89-895442 @ 1993-06-29 03:20 UTC (permalink / raw) To: legacy A coleague of mine was at a conference in Singapore last week and ran into Mr Stonebraker. He mentioned the fact that we were using postgres pretty solidly and well one thing led to another and Mr Stonebraker said that there was a commercial version of portgres available called MIRO. Does anyone have any details on this. If so, is it true? How do a get a copy? How good is it? Any other answers to questions that I haven't asked but that may be interesting. Thanks Chris Bunting Database Manager NT Dept of Mines and Energy PO Box 2901 DARWIN NT 0801 AUSTRALIA email bunting.dme.nt.gov.au voice 61-89-895442 fax 61-89-817861 ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: MIRO @ 1993-06-29 15:56 Jean Anderson <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Jean Anderson @ 1993-06-29 15:56 UTC (permalink / raw) To: legacy [email protected] (Chris Bunting 61-89-895442) writes: > ... Mr Stonebraker said that there was a \ > commercial version of portgres available called MIRO. > ... >If so, is it true? Yes; it's true. It's out in beta. I understand they plan on going production in mid August. > How do a get a copy? Miro Systems, Inc. 2000 Powell Street, Suite 1405 Emeryville, CA 94603 USA (510)652-8000 > How good is it? Here are a few impressions from looking at the user guide while the purchase order wheels at my company grind. I haven't paid much attention to the snazzy side; I've been focusing on "libmiro" to make sure the call interface has the hooks we require. My initial impressions from the docs are that it has retained the "best" of Postgres, while adding the "production" touches I expect in a commercial product: o Error handling is clean. You can snag both the error message and an error code. o Transaction management is ACID ("atomic, consistent, isolatable, durable"). There are a couple books out that describe ACID in excrutiating detail, if anybody is interested in references. o Connect services are good (some carry-overs from Postgres, some new features): - They have user names and passwords. - You can do multiple, concurrent connects. - They have a re-connect, which is a nice touch. We have coded the same thing for the other databases we work with, but we lose all database resources associated with the broken connect. - You can verify the connection is still live (of the products I work with, only Sybase can do that). o Query processing (especially results handling) is straight forward. o The docs look pretty good. And, of course, it talks SQL, important to the SQL-ers I work with. I'm not doing justice to the product by incompletely highlighting a few nit picky things; but Lance Gatrell made a good point in some recent email: > I would not use Postgres in a delivered product. .... Its not appropriate > for critical applications I quibble about what is meant by "critical"; but the point is well taken. I am wildly enthusiastic about Postgres functionality. But, at the risk of offending all the hard-working Postgres developers, I would hesitate installing it at remote, database-novice, 7x24 sites. I'm hoping Miro can satisfy those "production" needs. Remember, these impressions are based on docs; they are not based on "hands on" experience. These are my opinions, not my employer's, I don't work for Miro, #include <disclaimer>, etc. etc. - jean +-----------------------------------------------------------------------+ | Jean Anderson, DBA email: [email protected] | | SAIC Open Systems Division, MS A2-F | | 10210 Campus Point Drive phone: (619)458-2727 | | San Diego, CA 92121 fax: (619)458-4993 | +-----------------------------------------------------------------------+ ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Miro @ 1993-09-24 15:29 Lou D. Langholtz <[email protected]> parent: David Rich <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Lou D. Langholtz @ 1993-09-24 15:29 UTC (permalink / raw) To: [email protected]; +Cc: legacy > . . . > We are considering buying a license and would love to hear from > somebody that already has one. > > -- David Me to. Thanks! -- Lou ^ permalink raw reply [nested|flat] 5+ messages in thread
* Miro @ 1993-09-24 16:08 David Rich <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: David Rich @ 1993-09-24 16:08 UTC (permalink / raw) To: legacy I'm not sure if this question is out of bounds for this mailing list, but; are there any users of Miro out there? We are considering buying a license and would love to hear from somebody that already has one. -- David ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Miro @ 1993-09-28 15:33 Jean Anderson <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Jean Anderson @ 1993-09-28 15:33 UTC (permalink / raw) To: legacy [email protected] (David Rich 617/873-2634) writes: > I'm not sure if this question is out of bounds for this mailing list, > but; are there any users of Miro out there? [email protected] (Lou D. Langholtz) writes: > Me to. Thanks! Yes, there are Miro users out there. Back in June I posted a note describing what I knew about Miro from looking at the beta docs. I also invited folks to ping me once I had been actually using it. With many pings filling up my active mbox, this is a great time to reply to all pings with a single pong. [A side note to any vendors reading this: please keep the occasional mention of other products in perspective. I like you all. :-) ] My main focus has been on libmiro; once I have hooks in place for our existing applications, I'll tackle the snazzy Miro features. Specific notes (mostly libmiro): =============================== o Connect services: - Multiple concurrent connects work fine and I haven't encountered any collisions yet running side by side with Postgres, Oracle, and Sybase. - You can associate your own programmatic "thingy", whatever that might be, with a specific miro connection (very handy). - Other little touches show nice forethought, such as a function that returns the version of libmiro. o Error handling: - Services are outstanding, more flexible than any other product we use. o Concurrency control: - Everybody wants to know about deadlock management, of course. :-) It's easy to detect deadlock so you can properly retry. - You can also set the timeout (nice!). I found when I reduced the timeout to 10 seconds, I had trouble getting collisions to occur on my concurrency test; it wasn't until I had 6-8 concurrent processes whacking away at the same resource that they'd deadlock. I took the concurrency test up to 10 and had no problems. This was an important milestone for my more anxious users. o Query management: - Query results handling is work-in-progress (stay tuned). So far it looks good. o Docs (warning -- inbound flames): - Surprisingly accurate for such a new product. I found fewer doc errors than in Oracle's docs, and none of them were any big deal. - Like Sybase, and unlike Oracle (#$@!), Miro documents known problems up front. o Support: - One of the advantages of being in a small user base so far is you get swift, technically excellent responses. - Training is similarly impressive; the instructor is more technically knowledgeable than what I have experienced with other vendors. So far I haven't hit up against anything that I felt I couldn't live with; in fact quite the opposite. These are just my opinions, not my employer's, etc. etc. regards, -jean +-----------------------------------------------------------------------+ | Jean Anderson, DBA email: [email protected] | | SAIC Open Systems Division, MS A2-F | | 10210 Campus Point Drive phone: (619)458-2727 | | San Diego, CA 92121 fax: (619)458-4993 | +-----------------------------------------------------------------------+ | #ifdef MIRO | | return disclaimer('mine'); | | #elif ORACLE | | execute disclaimer(opinion => 'mine'); | | #elif POSTGRES | | retrieve (opinion=disclaimer("mine")) | | #elif SYBASE | | execute disclaimer @opinion="mine" | | #endif | +-----------------------------------------------------------------------+ ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~1993-09-28 15:33 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 1993-06-29 03:20 MIRO Chris Bunting 61-89-895442 <[email protected]> 1993-06-29 15:56 Re: MIRO Jean Anderson <[email protected]> 1993-09-24 16:08 Miro David Rich <[email protected]> 1993-09-24 15:29 ` Re: Miro Lou D. Langholtz <[email protected]> 1993-09-28 15:33 Re: Miro Jean Anderson <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox