SEO
vBulletin Search Engine Optimization
| |||||||
![Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.](http://unixadmintalk.com/iconimages/f47/re-committers-pgsql-change-fetch-move-use-int8_ltr.gif)
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-18-2008, 08:57 AM
| ||||
| ||||
 Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8. Tom Lane wrote: > momjian@postgresql.org (Bruce Momjian) writes: > > Log Message: > > ----------- > > Change FETCH/MOVE to use int8. > > This patch has broken half the buildfarm, and I've still not seen a > rationale why we need to make such a change at all. Fixed with attached patch. The use case for this was not FETCH, but MOVE for > 2gig tables. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org      |
|
04-18-2008, 08:57 AM
| |||
| |||
| Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8. Bruce Momjian <bruce@momjian.us> writes: >> This patch has broken half the buildfarm, and I've still not seen a >> rationale why we need to make such a change at all. > Fixed with attached patch. The use case for this was not FETCH, but > MOVE for > 2gig tables. There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD ALL does not need this to work for >2G tables). It is not worth the extra computational cycles that it imposes on every machine whether they use the feature or not, and it is certainly not worth the developer time we're expending to fix this poorly written patch. Please revert it. regards, tom lane ---------------------------(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 |
|
04-18-2008, 08:57 AM
| |||
| |||
| Re: [HACKERS] [COMMITTERS] pgsql: Change FETCH/MOVE Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > >> This patch has broken half the buildfarm, and I've still not seen a > >> rationale why we need to make such a change at all. > > > Fixed with attached patch. The use case for this was not FETCH, but > > MOVE for > 2gig tables. > > There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD > ALL does not need this to work for >2G tables). It is not worth the > extra computational cycles that it imposes on every machine whether they > use the feature or not, and it is certainly not worth the developer time > we're expending to fix this poorly written patch. Please revert it. Already done because of bad coding. You want the TODO item removed too? -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(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 |
|
04-18-2008, 08:57 AM
| |||
| |||
| Re: [HACKERS] [COMMITTERS] pgsql: Change FETCH/MOVE to use int8. Bruce Momjian <bruce@momjian.us> writes: > Tom Lane wrote: >> There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD >> ALL does not need this to work for >2G tables). > Already done because of bad coding. You want the TODO item removed too? As I said, I see no use case for it. Maybe if Moore's Law holds up for another five or ten years, it'll look like a useful feature then ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
|
04-18-2008, 08:57 AM
| ||||
| ||||
| Re: [HACKERS] [COMMITTERS] pgsql: Change FETCH/MOVE Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Tom Lane wrote: > >> There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD > >> ALL does not need this to work for >2G tables). > > > Already done because of bad coding. You want the TODO item removed too? > > As I said, I see no use case for it. Maybe if Moore's Law holds up for > another five or ten years, it'll look like a useful feature then ... Removed. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
Linear Mode
