Thread: Problem with web search
Does anyone know why this email: http://archives.postgresql.org/pgsql-hackers/2007-10/msg01470.php cannot be found via a Postgres web site search for "causes dyld errors": http://search.postgresql.org/search?m=1&q=%22causes+dyld+errors%22&l=&d=&s= In fact no search will find it. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Bruce Momjian wrote: > Does anyone know why this email: > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01470.php > > cannot be found via a Postgres web site search for "causes dyld errors": > > http://search.postgresql.org/search?m=1&q=%22causes+dyld+errors%22&l=&d=&s= > > In fact no search will find it. > Hmm, that's not the only thing. The list archive search isn't up to date. The reason for this is that the search machine has a hardcoded address in /etc/hosts for archives.postgresql.org - which points to the machine *before* the move JD made. So, JD... Any reason it needs to be there? If so, it should just be updated to point to the new one, I think? Once that's done, we'll need to forcibly reindex october and november. //Magnus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 09 Nov 2007 22:54:49 +0100 Magnus Hagander <magnus@hagander.net> wrote: > Bruce Momjian wrote: > > Does anyone know why this email: > > > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01470.php > > > > cannot be found via a Postgres web site search for "causes dyld > > errors": > > > > http://search.postgresql.org/search?m=1&q=%22causes+dyld+errors%22&l=&d=&s= > > > > In fact no search will find it. > > > > Hmm, that's not the only thing. The list archive search isn't up to > date. The reason for this is that the search machine has a hardcoded > address in /etc/hosts for archives.postgresql.org - which points to > the machine *before* the move JD made. > > So, JD... Any reason it needs to be there? If so, it should just be > updated to point to the new one, I think? Once that's done, we'll need > to forcibly reindex october and november. No I think the host entry was there from when we initially moved it to make things work. I have removed it, and verified that the resolver picks up the correct new address. Joshua D. Drake > > > > //Magnus > > > ---------------------------(end of > broadcast)--------------------------- TIP 2: Don't 'kill -9' the > postmaster > - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHNNfMATb/zqfZUUQRAnA6AJ9S3OzHRvaX8lUqz4MVzr0YuzJjVQCcDOUe Mr++ZzBBocMEme5Klu0w3Og= =22IK -----END PGP SIGNATURE-----
Joshua D. Drake wrote: > On Fri, 09 Nov 2007 22:54:49 +0100 > Magnus Hagander <magnus@hagander.net> wrote: > >> Bruce Momjian wrote: >>> Does anyone know why this email: >>> >>> http://archives.postgresql.org/pgsql-hackers/2007-10/msg01470.php >>> >>> cannot be found via a Postgres web site search for "causes dyld >>> errors": >>> >>> http://search.postgresql.org/search?m=1&q=%22causes+dyld+errors%22&l=&d=&s= >>> >>> In fact no search will find it. >>> >> Hmm, that's not the only thing. The list archive search isn't up to >> date. The reason for this is that the search machine has a hardcoded >> address in /etc/hosts for archives.postgresql.org - which points to >> the machine *before* the move JD made. > >> So, JD... Any reason it needs to be there? If so, it should just be >> updated to point to the new one, I think? Once that's done, we'll need >> to forcibly reindex october and november. > > No I think the host entry was there from when we initially moved it to > make things work. I have removed it, and verified that the resolver > picks up the correct new address. Archives are updated, and that search now works, as do others for things that happened in oct and nov. //Magnus