vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Folks, I'm not getting bug reports for 8.2 from inside Sun. However, I'm not sure how I can determine from the source what build day a particular snapshot instance is from -- sometimes these files get copied around a bit before being built. Is there a file somewhere that would carry a timestamp inside it? Thanks. -- Josh Berkus PostgreSQL @ Sun San Francisco ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| |||
| Josh Berkus <josh@agliodbs.com> writes: > I'm not getting bug reports for 8.2 from inside Sun. However, I'm not sure > how I can determine from the source what build day a particular snapshot > instance is from -- sometimes these files get copied around a bit before > being built. Is there a file somewhere that would carry a timestamp inside > it? Well, you could grep for the latest $PostgreSQL$ header line's commit date, but I kinda wonder why exactly you should need to do that. If you don't know when you pulled the snapshot you are testing, I submit you have a process problem you ought to fix. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
| |||
| Tom, > Well, you could grep for the latest $PostgreSQL$ header line's commit > date, but I kinda wonder why exactly you should need to do that. If you > don't know when you pulled the snapshot you are testing, I submit you > have a process problem you ought to fix. These aren't PostgreSQL test people, but folks from Java and the like testing other stuff. And they're pulling the build from ftp:/pub/dev/, not from CVS. -- Josh Berkus PostgreSQL @ Sun San Francisco ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
| |||
| Josh, > >> Well, you could grep for the latest $PostgreSQL$ header line's commit > >> date, but I kinda wonder why exactly you should need to do that. If you > >> don't know when you pulled the snapshot you are testing, I submit you > >> have a process problem you ought to fix. > > > > These aren't PostgreSQL test people, but folks from Java and the like > > testing other stuff. And they're pulling the build from ftp:/pub/dev/, > > not from CVS. > > O.k. but why aren't they submitting pgsql-bugs? Believe me, you don't want these people submitting bugs unfiltered by me. Especially since they can't remember when they grabbed the snapshot. Seriously, though, it would be an aid to testing if we could add a tag to the version or README file or something for the pgsql-snapshot that told us build date. If there is one, I can't find it. When Marc gets done putting out fires, I'll ask him how difficult that would be. -- Josh Berkus PostgreSQL @ Sun San Francisco ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| |||
| Josh Berkus wrote: > Josh, > >>>> Well, you could grep for the latest $PostgreSQL$ header line's commit >>>> date, but I kinda wonder why exactly you should need to do that. If you >>>> don't know when you pulled the snapshot you are testing, I submit you >>>> have a process problem you ought to fix. >>> These aren't PostgreSQL test people, but folks from Java and the like >>> testing other stuff. And they're pulling the build from ftp:/pub/dev/, >>> not from CVS. >> O.k. but why aren't they submitting pgsql-bugs? > > Believe me, you don't want these people submitting bugs unfiltered by me. > Especially since they can't remember when they grabbed the snapshot. Heh, o.k. I can definitely respect that Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
| |||
| Josh Berkus wrote: > Tom, > >> Well, you could grep for the latest $PostgreSQL$ header line's commit >> date, but I kinda wonder why exactly you should need to do that. If you >> don't know when you pulled the snapshot you are testing, I submit you >> have a process problem you ought to fix. > > These aren't PostgreSQL test people, but folks from Java and the like testing > other stuff. And they're pulling the build from ftp:/pub/dev/, not from CVS. > O.k. but why aren't they submitting pgsql-bugs? Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
| |||
| On Wed, 6 Sep 2006, Josh Berkus wrote: > Josh, > >>>> Well, you could grep for the latest $PostgreSQL$ header line's commit >>>> date, but I kinda wonder why exactly you should need to do that. If you >>>> don't know when you pulled the snapshot you are testing, I submit you >>>> have a process problem you ought to fix. >>> >>> These aren't PostgreSQL test people, but folks from Java and the like >>> testing other stuff. And they're pulling the build from ftp:/pub/dev/, >>> not from CVS. >> >> O.k. but why aren't they submitting pgsql-bugs? > > Believe me, you don't want these people submitting bugs unfiltered by me. > Especially since they can't remember when they grabbed the snapshot. > > Seriously, though, it would be an aid to testing if we could add a tag to the > version or README file or something for the pgsql-snapshot that told us build > date. How about adding a simple: 'touch snapshotdate' .. in the root directory? Would that suffice? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
| ||||
| On Thursday 07 September 2006 01:24, Marc G. Fournier wrote: > > How about adding a simple: 'touch snapshotdate' .. in the root directory? > Would that suffice? I'd say date "+[something]" > snapshotdate I betcha that people that can't remember trivial things will muck up file timestamps by copying jan -- -------------------------------------------------------------- Jan de Visser * * * * * * * * * * jdevisser@digitalfairway.com * * * * * * * * Baruk Khazad! Khazad ai-menu! -------------------------------------------------------------- ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |