On Sat, Jun 30, 2018 at 5:38 PM, Tom Lane wrote:
> I also think that there's some horribly unsafe coding in
> apply_scanjoin_target_to_paths: it clobbers a RelOptInfo's reltarget,
> with no thought for whether that might affect things elsewhere,
> and it also clobbers individual paths'
I wrote:
> "Regina Obe" writes:
>> Here is a trivial example to exercise that doesn't involve PostGIS.
>> CREATE TABLE edge AS SELECT 1 AS edge_id;
>> SELECT 't3280', 'L1b' || generate_series(1,10)
>> FROM edge
>> ORDER BY 1;
> That's odd. It works fine in HEAD but not the v10 branch. I
> "Regina Obe" writes:
> > Here is a trivial example to exercise that doesn't involve PostGIS.
>
> > CREATE TABLE edge AS SELECT 1 AS edge_id; SELECT 't3280', 'L1b' ||
> > generate_series(1,10) FROM edge ORDER BY 1;
>
> That's odd. It works fine in HEAD but not the v10 branch. I suspect that
"Regina Obe" writes:
> Here is a trivial example to exercise that doesn't involve PostGIS.
> CREATE TABLE edge AS SELECT 1 AS edge_id;
> SELECT 't3280', 'L1b' || generate_series(1,10)
> FROM edge
> ORDER BY 1;
That's odd. It works fine in HEAD but not the v10 branch. I suspect
that the fix
On 29 June 2018 at 21:06, Regina Obe wrote:
> I think the exact query that is triggering it is this one though I don't
> have PostgreSQL 10 head installed locally to confirm.
>
> SELECT 't3280', 'L1b' || topology.TopoGeo_AddLinestring('bug3280', geom)
> FROM bug3280.edge where edge_id = 1
>
