On 3/13/13 7:10 PM, Ants Aasma wrote:
On Thu, Mar 14, 2013 at 1:51 AM, Jim Nasby j...@nasby.net wrote:
On 3/12/13 9:10 AM, Ants Aasma wrote:
I have a feeling this is an increasingly widespread pattern with a
proliferation of mobile devices that need syncing.
If you're doing that with
On 3/12/13 9:10 AM, Ants Aasma wrote:
I have a feeling this is an increasingly widespread pattern with a
proliferation of mobile devices that need syncing.
If you're doing that with timestamps you're asking for a slew of problems, not
all of which can be solved by just adding some random
On Thu, Mar 14, 2013 at 1:51 AM, Jim Nasby j...@nasby.net wrote:
On 3/12/13 9:10 AM, Ants Aasma wrote:
I have a feeling this is an increasingly widespread pattern with a
proliferation of mobile devices that need syncing.
If you're doing that with timestamps you're asking for a slew of
On Mon, Mar 11, 2013 at 9:13 PM, Greg Stark st...@mit.edu wrote:
On Thu, Mar 7, 2013 at 12:51 AM, Jim Nasby j...@nasby.net wrote:
Something worth considering on this... I suspect it's possible to use an
index-only scan to do this, regardless of whether the heap page is all
visible. The reason
On Thu, Mar 7, 2013 at 12:51 AM, Jim Nasby j...@nasby.net wrote:
Something worth considering on this... I suspect it's possible to use an
index-only scan to do this, regardless of whether the heap page is all
visible. The reason is that the newly created index would just use the same
access
On 2/2/13 4:05 AM, Paul Norman wrote:
Hello,
After a discussion on IRC in #postgresql, I had a feature suggestion and it
was suggested I write it up here.
I have a large (200GB, 1.7b rows) table with a number of columns, but the
two of interest here are a hstore column, tags and a postgis
Hello,
After a discussion on IRC in #postgresql, I had a feature suggestion and it
was suggested I write it up here.
I have a large (200GB, 1.7b rows) table with a number of columns, but the
two of interest here are a hstore column, tags and a postgis geometry
column, geom.
There is a GIN index
