| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
| Cc: | Florian Weimer <Weimer(at)CERT(dot)Uni-Stuttgart(dot)DE>, Thomas Lockhart <thomas(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql-server/src include/utils/timestamp.h bac ... |
| Date: | 2002-08-04 23:03:10 |
| Message-ID: | 3D4DB2AE.950BC98C@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
...
> Thomas can correct me if I'm mistaken, but I believe these changes apply
> to the new integer datetime code Thomas wrote earlier in the 7.3
> development cycle -- i.e. there's no bug present in 7.2, or earlier CVS
> code when compiled without --enable-integer-datetimes.
Actually, it is probably an issue for the earlier stuff too, but the
integer value reading seems to have different sensitivities to really
long strings which is the symptom that was noticed just recently.
The same technique for guarding would work fine for 7.2 also.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-04 23:46:39 | pgsql-server/src/include/catalog pg_proc.h |
| Previous Message | Joe Conway | 2002-08-04 22:50:37 | Re: pgsql-server/src/backend catalog/pg_proc.c nod ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-04 23:17:49 | Re: FUNC_MAX_ARGS benchmarks |
| Previous Message | Neil Conway | 2002-08-04 22:45:46 | Re: [COMMITTERS] pgsql-server/src include/utils/timestamp.h bac ... |