Thread: Late night problems
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Quick late-night surfing notes on the main page: Linux and Windows should always be capitalized (OpenOffice article) OSCON article misspells "presence" as "presense" archives.postgresql.org (and search.postgresql.org) are embarassingly slow. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200406280014 -----BEGIN PGP SIGNATURE----- iD8DBQFA350fvJuQZxSWSsgRAtsLAJ47gGAnALnf2t42KShBlx4BKEyaiwCg04q6 2iUQiYfniCrnDkKRESnsFfw= =MvcO -----END PGP SIGNATURE-----
Greg Sabino Mullane wrote: <snip> > Linux and Windows should always be capitalized (OpenOffice article) > > OSCON article misspells "presence" as "presense" Thanks Greg. Just updated those bits, but not the slowness things. When the automatic page rebuild happens the changes will become end user visible. :) Regards and best wishes, Justin Clift > archives.postgresql.org (and search.postgresql.org) are > embarassingly slow. <snip>
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Greg > Sabino Mullane > Sent: 28 June 2004 05:22 > To: pgsql-www@postgresql.org > Subject: [pgsql-www] Late night problems > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Quick late-night surfing notes on the main page: > > Linux and Windows should always be capitalized (OpenOffice article) Looks like someone already fixed this. > OSCON article misspells "presence" as "presense" And this. > archives.postgresql.org (and search.postgresql.org) are > embarassingly slow. I don't see this from .uk. In fact, search.postgresql.org has just recently been moved to new hardware in .au which offers far greater performance - for example, I just searched then entire database for 'referential integrity' and saw the results page, including all images and ads in about 3 seconds. Thanks for the feedback though... Regards, Dave
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I don't see this from .uk. In fact, search.postgresql.org has just > recently been moved to new hardware in .au which offers far greater > performance - for example, I just searched then entire database for > 'referential integrity' and saw the results page, including all images > and ads in about 3 seconds. Seems to be better now. Just now, searching for "speed" in the archives took "0.060" seconds according to the results pae. Last night, it took 108 seconds. Even navigating from one message to the next in a thread took about 20 seconds for each page to load. This has happened before: I'll whip up a cron script to track basic responsiveness over time. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200406280647 -----BEGIN PGP SIGNATURE----- iD8DBQFA3/gevJuQZxSWSsgRAm2SAJ9r8XBTTl57gwexKNRt6V+C79M6KQCeItos thfSOg9fPj4sc9DwPMVA8So= =54Ol -----END PGP SIGNATURE-----
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Greg > Sabino Mullane > Sent: 28 June 2004 11:49 > To: pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Late night problems > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > I don't see this from .uk. In fact, search.postgresql.org has just > > recently been moved to new hardware in .au which offers far greater > > performance - for example, I just searched then entire database for > > 'referential integrity' and saw the results page, including > all images > > and ads in about 3 seconds. > > Seems to be better now. Just now, searching for "speed" in > the archives took "0.060" seconds according to the results > pae. Last night, it took 108 seconds. Even navigating from > one message to the next in a thread took about 20 seconds for > each page to load. This has happened > before: I'll whip up a cron script to track basic > responsiveness over time. OK, that sounds like it'll be useful. Might be worth talking to John Hansen (who's on this list now) about it seeing as he's donating all the CPU/disk/connectivity... Regards, Dave.
Ahhhh Sunday night = vacuum full on the database :( Cron job removed... Regards, John > -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Greg > Sabino Mullane > Sent: Monday, 28 June 2004 8:49 PM > To: pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Late night problems > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > I don't see this from .uk. In fact, search.postgresql.org has just > > recently been moved to new hardware in .au which offers far greater > > performance - for example, I just searched then entire database for > > 'referential integrity' and saw the results page, including > all images > > and ads in about 3 seconds. > > Seems to be better now. Just now, searching for "speed" in > the archives took "0.060" seconds according to the results > pae. Last night, it took 108 seconds. Even navigating from > one message to the next in a thread took about 20 seconds for > each page to load. This has happened > before: I'll whip up a cron script to track basic > responsiveness over time. > > - -- > Greg Sabino Mullane greg@turnstep.com > PGP Key: 0x14964AC8 200406280647 > > -----BEGIN PGP SIGNATURE----- > > iD8DBQFA3/gevJuQZxSWSsgRAm2SAJ9r8XBTTl57gwexKNRt6V+C79M6KQCeItos > thfSOg9fPj4sc9DwPMVA8So= > =54Ol > -----END PGP SIGNATURE----- > > > > ---------------------------(end of > broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index > scan if your > joining column's datatypes do not match > >
"Dave Page" <dpage@vale-housing.co.uk> writes:
> I don't see this from .uk. In fact, search.postgresql.org has just
> recently been moved to new hardware in .au which offers far greater
> performance - for example, I just searched then entire database for
> 'referential integrity' and saw the results page, including all images
> and ads in about 3 seconds.
The search seems fast, but I see no results, just a blank page :-(
In the past this has usually been because of bad HTML, eg an unclosed
<table> definition. Could someone run an HTML validator over the output?
regards, tom lane
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: 28 June 2004 15:22 > To: Dave Page > Cc: Greg Sabino Mullane; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Late night problems > > "Dave Page" <dpage@vale-housing.co.uk> writes: > > I don't see this from .uk. In fact, search.postgresql.org has just > > recently been moved to new hardware in .au which offers far greater > > performance - for example, I just searched then entire database for > > 'referential integrity' and saw the results page, including > all images > > and ads in about 3 seconds. > > The search seems fast, but I see no results, just a blank > page :-( In the past this has usually been because of bad > HTML, eg an unclosed <table> definition. Could someone run > an HTML validator over the output? John, can you take a look at the archives template please? Tom; is the main search page working OK? It didn't seem to have any close tag errors like the archives. (http://search.postgresql.org/www.search) From archives: Line 490, column 8: end tag for "TABLE" omitted, but its declaration does not permit this </CENTER> Line 13, column 0: start tag was here <TABLE WIDTH="700"> Line 492, column 7: "HEAD" not finished but document ended </HTML> Line 492, column 7: "HTML" not finished but document ended </HTML> Regards, Dave
"Dave Page" <dpage@vale-housing.co.uk> writes: > Tom; is the main search page working OK? It didn't seem to have any > close tag errors like the archives. > (http://search.postgresql.org/www.search) That one works; it's the result of searching at http://archives.postgresql.org/ that has issues. (The main search page has some presentation problems of its own, mainly that it won't adapt to my window width, but at least I can use it.) I think the unclosed tag in the archives search is probably from one of the component tables; the top-level tags all seem to be closed off properly at the end of the page. regards, tom lane
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: 28 June 2004 15:41 > To: Dave Page > Cc: John Hansen; Greg Sabino Mullane; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Late night problems > > "Dave Page" <dpage@vale-housing.co.uk> writes: > > Tom; is the main search page working OK? It didn't seem to have any > > close tag errors like the archives. > > (http://search.postgresql.org/www.search) > > That one works; it's the result of searching at > http://archives.postgresql.org/ that has issues. > > (The main search page has some presentation problems of its > own, mainly that it won't adapt to my window width, but at > least I can use it.) Do you mean because it's fixed width? If so, that's by design. That'll change in the new version of the site. > I think the unclosed tag in the archives search is probably > from one of the component tables; the top-level tags all seem > to be closed off properly at the end of the page. Doesn't overly surprise me. The search templates can get quite complex and are not the easiest things to debug. I don't suppose there's any chace of persuading you to upgrade to Firefox or something yet is there? :-) Regards, Dave.
On Mon, 28 Jun 2004, Greg Sabino Mullane wrote: > ------------------------------------------------------------------------------ > /usr/local/libexec/ppf_verify: pgp command failed > > gpg: WARNING: using insecure memory! > gpg: please see http://www.gnupg.org/faq.html for more information > gpg: Signature made Mon Jun 28 01:22:55 2004 ADT using DSA key ID 14964AC8 > gpg: Can't check signature: public key not found > ------------------------------------------------------------------------------ > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Quick late-night surfing notes on the main page: > > Linux and Windows should always be capitalized (OpenOffice article) > > OSCON article misspells "presence" as "presense" > > archives.postgresql.org (and search.postgresql.org) are > embarassingly slow. I'm working on this one ... I've having a bugger of a time finding a suitable rack chassis for hte dual-athlon's though :( if anyone has any suggestions, please feel free to make it, but at this time, it looks like I'm going to be going Dual-Xeon :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Acme make some reasonable generic ATX rack cases: http://www.acme-technology.co.uk/ Dunno if they'll ship to you though. /D -----Original Message----- From: pgsql-www-owner@postgresql.org on behalf of Marc G. Fournier Sent: Mon 6/28/2004 6:03 PM To: Greg Sabino Mullane Cc: pgsql-www@postgresql.org Subject: Re: [pgsql-www] Late night problems I'm working on this one ... I've having a bugger of a time finding a suitable rack chassis for hte dual-athlon's though :( if anyone has any suggestions, please feel free to make it, but at this time, it looks like I'm going to be going Dual-Xeon :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Another good reason to use XML/XSL. I'll fix it up tomorrow night, and use XML/XSL :). Gonna go to bed now,. Have a big day full of meetings tomorra. ... John > -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Dave Page > Sent: Tuesday, 29 June 2004 12:34 AM > To: Tom Lane; John Hansen > Cc: Greg Sabino Mullane; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Late night problems > > > > > -----Original Message----- > > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > > Sent: 28 June 2004 15:22 > > To: Dave Page > > Cc: Greg Sabino Mullane; pgsql-www@postgresql.org > > Subject: Re: [pgsql-www] Late night problems > > > > "Dave Page" <dpage@vale-housing.co.uk> writes: > > > I don't see this from .uk. In fact, search.postgresql.org > has just > > > recently been moved to new hardware in .au which offers > far greater > > > performance - for example, I just searched then entire > database for > > > 'referential integrity' and saw the results page, including > > all images > > > and ads in about 3 seconds. > > > > The search seems fast, but I see no results, just a blank > page :-( In > > the past this has usually been because of bad HTML, eg an unclosed > > <table> definition. Could someone run an HTML validator over the > > output? > > John, can you take a look at the archives template please? > > > Tom; is the main search page working OK? It didn't seem to > have any close tag errors like the archives. > (http://search.postgresql.org/www.search) > > > From archives: > > Line 490, column 8: end tag for "TABLE" omitted, but its > declaration does not permit this </CENTER> > > Line 13, column 0: start tag was here > <TABLE WIDTH="700"> > > Line 492, column 7: "HEAD" not finished but document ended </HTML> > > Line 492, column 7: "HTML" not finished but document ended </HTML> > > > Regards, Dave > > ---------------------------(end of > broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to > majordomo@postgresql.org) > >
Guys I think it's fixed. See if that's better,... haven't done the XML/XSL yet tho, also, Dave your datevars patch seems to have a problem with the OPTION tags when they're INDENTED, could you have a look at that? Regards, John On Tue, 2004-06-29 at 00:33, Dave Page wrote: > > > -----Original Message----- > > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > > Sent: 28 June 2004 15:22 > > To: Dave Page > > Cc: Greg Sabino Mullane; pgsql-www@postgresql.org > > Subject: Re: [pgsql-www] Late night problems > > > > "Dave Page" <dpage@vale-housing.co.uk> writes: > > > I don't see this from .uk. In fact, search.postgresql.org has just > > > recently been moved to new hardware in .au which offers far greater > > > performance - for example, I just searched then entire database for > > > 'referential integrity' and saw the results page, including > > all images > > > and ads in about 3 seconds. > > > > The search seems fast, but I see no results, just a blank > > page :-( In the past this has usually been because of bad > > HTML, eg an unclosed <table> definition. Could someone run > > an HTML validator over the output? > > John, can you take a look at the archives template please? > > > Tom; is the main search page working OK? It didn't seem to have any > close tag errors like the archives. > (http://search.postgresql.org/www.search) > > > From archives: > > Line 490, column 8: end tag for "TABLE" omitted, but its declaration > does not permit this > </CENTER> > > Line 13, column 0: start tag was here > <TABLE WIDTH="700"> > > Line 492, column 7: "HEAD" not finished but document ended > </HTML> > > Line 492, column 7: "HTML" not finished but document ended > </HTML> > > > Regards, Dave
> -----Original Message----- > From: John Hansen [mailto:john@geeknet.com.au] > Sent: 30 June 2004 04:36 > To: Dave Page > Cc: Tom Lane; Greg Sabino Mullane; pgsql-www@postgresql.org > Subject: RE: [pgsql-www] Late night problems > > Guys > > I think it's fixed. > > See if that's better,... haven't done the XML/XSL yet tho, > > also, Dave your datevars patch seems to have a problem with > the OPTION tags when they're INDENTED, could you have a look at that? That patch just extended the existing code for a few extra variables. If it's having trouble reading them when they're indented, then it'll be the parser code thats at fault. Regards, Dave.
John Hansen <john@geeknet.com.au> writes:
> I think it's fixed.
Works for me now (and fast too). Many thanks!
regards, tom lane
Sweet, ... john > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Wednesday, 30 June 2004 11:58 PM > To: John Hansen > Cc: Dave Page; Greg Sabino Mullane; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Late night problems > > John Hansen <john@geeknet.com.au> writes: > > I think it's fixed. > > Works for me now (and fast too). Many thanks! > > regards, tom lane > >