| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Chris Dunlop <chris(at)onthe(dot)net(dot)au>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Australian timezone configure option |
| Date: | 2001-06-14 01:20:30 |
| Message-ID: | 15692.992481630@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>> Now I'm going to object LOUDLY. You cannot convince me that the above
>> is a good implementation --- it's a complete crock, and will break the
>> instant someone looks at it sidewise.
> But it hasn't broken in years of use and maintenance, so that does not
> sound like an issue.
Uh, I was complaining about Bruce's idea of scribbling on the datetkn
table and expecting that to change what the datecache records. That's
not something we've been doing for years and years, and no I don't think
it's maintainable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chris.bitmead | 2001-06-14 01:21:46 | Re: [PATCHES] Australian timezone configure option |
| Previous Message | Joe Conway | 2001-06-14 01:19:52 | Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-14 01:27:20 | Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal |
| Previous Message | Joe Conway | 2001-06-14 01:19:52 | Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal |