Re: [HACKERS] [PERFORM] Slow count(*) again...
On 2011-02-03 22:48, Scott Marlowe wrote: On Thu, Feb 3, 2011 at 8:40 PM, Greg Smith wrote: Scott Marlowe wrote: Yes they're useful, but like a plastic bad covering a broken car window, they're useful because they cover something that's inherently broken. Awesome. Now we have a car anology, with a funny typo no less. "Plastic bad", I love it. This is real progress toward getting all the common list argument idioms aired out. All we need now is a homage to Mike Godwin and we can close this down. It's not so much a car analogy as a plastic bad analogy. Don't be such an analogy Nazi. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
Re: [PERFORM] Decide between Postgresql and Mysql (help of
On Wednesday 29 March 2006 22:01, Craig A. James wrote: > This is off-topic for this group so I'll just give a brief reply; I'm happy > to carry on more just between the two of us... > > Gorshkov wrote: > > That being said . what *is* the difference between coding a website - > > major or otherwise - in an "old-fashioned" compiled language and a > > non-compiled language, except for the amount of hoursepower and memory > > you require? > > > > Old-fashioned doesn't mean bad, inappropriate, or inferior. It's just not > > the latest-and-greatest, however it's currently defined by the geek > > fashion police. > > Our experience coding web sites with C/C++ versus Perl is about a factor of > ten in productivity. We only use C/C++ for CPU-intensive calculations, > such as scientific prediction code. Everything else is Perl or Java. > > I recently re-coded 10,000 lines of C into 650 lines of Perl. Why? String > handling, hash tables, and the simplicity of DBD/DBI. And there was no > loss of performance, because the app was strictly I/O bound (that is, > Postgres was I/O bound). Sure, the old app may not have been optimal, but > we're talking about a factor of 15 reduction in lines of code. Sounds to me like the C programmers in your past needed to learn how to re-use code and make libraries. That's not a function of the language - that's a function of the programmer. > > That's not "geek fashion", it's good engineering. Pick the best tool for > the job, and learn how to use it. > Thanks for making my point. You choose the best tool for the job, and sometimes it's "old-fashioned". Please remember that - there may be newbies out there who think that if they're not using the latest alpha-beta-zeta version .0006-a-r1, then they must be bad programmers. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PERFORM] Decide between Postgresql and Mysql (help of
On Wednesday 29 March 2006 21:23, Craig A. James wrote: > Gorshkov wrote: > > /flame on > > if you were *that* worried about performance, you wouldn't be using PHP > > or *any* interperted language > > /flame off > > > > sorry - couldn't resist it :-) > > I hope this was just a joke. You should be sure to clarify - there might > be some newbie out there who thinks you are seriously suggesting coding > major web sites in some old-fashioned compiled language. > well yes, it was meant as a joke . that's *usually* what a ";-)" means. That being said . what *is* the difference between coding a website - major or otherwise - in an "old-fashioned" compiled language and a non-compiled language, except for the amount of hoursepower and memory you require? Old-fashioned doesn't mean bad, inappropriate, or inferior. It's just not the latest-and-greatest, however it's currently defined by the geek fashion police. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PERFORM] Decide between Postgresql and Mysql (help of
On Tuesday 28 March 2006 14:50, Scott Marlowe wrote: > On Tue, 2006-03-28 at 13:42, PFC wrote: > > > This is as much about the code in front of the database as the database > > > itself. You'll want to use an architecture that supports pooled > > > connections (java, php under lighttpd, etc...) and you'll want to look > > > > Well, anybody who uses PHP and cares about performance is already using > > lighttpd, no ? /flame on if you were *that* worried about performance, you wouldn't be using PHP or *any* interperted language /flame off sorry - couldn't resist it :-) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[PERFORM] embedded postgres and threading
Sorry if this is the wrong list ... I'm in the process of developing an application based on gtk & postgress for both windows & linux. Short, simple and to the point - I'm using embedded SQL is there anything I should know about using postgress in multiple threads, under linux OR windows? I've not been able to find anything in the FAQ or documentation regarding this ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
