-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 08 December 2003 9:33 pm, Tom Lane wrote:
> In the absence of any brilliant insight, I'd suggest slogging through
> Gen_fmgrtab.sh to try to narrow down where functions are getting lost
> --- add code to save the various intermediate files, and see what's in
> 'em. If we knew exactly which step was losing the functions it'd be a
> leg up.
>
I just did this. I am no awk or sed expert. I can't see any faults in the
script other than it is difficult to read. My only thought is that some of
the regex behavior has changed, but I can't identify anything. The regexes
used here are very standard.
Unfortunately, in testing the bugger, it accidentally worked. I find this
most disturbing. However, I was pleasantly surprised that it failed at
least one more time before working properly.
Chalk the cause of this bug up as high-energy particles striking the memory
chip in just the right place at just the right time.
The only other thing I think might affect it is the fact that I was
simultaneously compiling PostgreSQL 7.3.4, reading email, and downloading
stuff. Perhaps there is a strange race condition in the make process. Of
course, the recent power outage in the area (that didn't affect us)
might've been a cause as well.
I apologize that I couldn't ease your pain, Tom. I know how it feels to see
the same bug pop up occasionally, only to be solved by hitting the "Redo"
key.
- --
Jonathan Gardner
[EMAIL PROTECTED]
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/1XQJWgwF3QvpWNwRAi0FAKCkPV+yn0y3kNT3AoHy5TX9a0v6NACaA7qI
PlIJfFguW4LNr+4RL535rIM=
=wWkP
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
