On Tue, Feb 25, 2014 at 3:13 PM, Eliot Gable wrote:
> On Tue, Feb 25, 2014 at 11:17 AM, David Johnston wrote:
>
>> David Johnston wrote
>> >
>> > Eliot Gable-4 wrote
>> >> I advocated creating a separate mapping table which
>> >> maps the ID of these records to the other ID we are searching for
On Tue, Feb 25, 2014 at 11:17 AM, David Johnston wrote:
> David Johnston wrote
> >
> > Eliot Gable-4 wrote
> >> I advocated creating a separate mapping table which
> >> maps the ID of these records to the other ID we are searching for and
> >> performing a JOIN on the two tables with appropriate
David Johnston wrote
>
> Eliot Gable-4 wrote
>> I advocated creating a separate mapping table which
>> maps the ID of these records to the other ID we are searching for and
>> performing a JOIN on the two tables with appropriate foreign key
>> relationships and indices. However, I was ask to inste
Eliot Gable-4 wrote
> I advocated creating a separate mapping table which
> maps the ID of these records to the other ID we are searching for and
> performing a JOIN on the two tables with appropriate foreign key
> relationships and indices. However, I was ask to instead put the list into
> a singl
On Tue, Feb 25, 2014 at 9:08 AM, Eliot Gable
wrote:
> If we wanted to put an index on a JSON data type column whose values was a
> simple array of IDs, what would the index look like, and how would we
> construct the query to make use of it?
For 9.0, your only option would be to use the intarray
I am working on a project for which I require some assistance. Any input
would be appreciated.
We have a table with millions of records and dozens of columns. On some
systems, it takes up >10GB of disk space, and it runs on a single disk
which is rather slow (7200 RPM). We typically don't do any c
