Can anyone tell me if this is a) expected b) a straight bug and stick it in github c) something we should see if we can fix without raising a bug?
Happy to dig deeper, but as its making postgres explode I assume its not an expected response.
Can anyone tell me if this is a) expected b) a straight bug and stick it in github c) something we should see if we can fix without raising a bug?
Happy to dig deeper, but as its making postgres explode I assume its not an expected response.