From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: nunks <nunks.lol@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Date: Wed, 6 Jun 2018 10:57:41 -0600
Message-ID: <3C61E858-5CA7-405D-B32A-B4C89D1AC62E@elevated-dev.com> (raw)
In-Reply-To: <CAOC+FBXehj4X2DMfytnPKHRWrWWZjq1G9OfUXsMop5Tex7hrvg@mail.gmail.com>
References: <CACq6szQbQDG6_mThyH32=6J0e99-KdqOrhZMm9QwvGoVFzNbBw@mail.gmail.com>
<CAOC+FBXehj4X2DMfytnPKHRWrWWZjq1G9OfUXsMop5Tex7hrvg@mail.gmail.com>
He's *NOT* doing anything that requires 1600 columns--that was pretty much the point of his post.
--
Scott Ribe
scott_ribe@elevated-dev.com
https://www.linkedin.com/in/scottribe/> On Jun 6, 2018, at 10:53 AM, Wells Oliver <wells.oliver@gmail.com> wrote:
>
> let's just stop for a moment and talk about what you're doing that requires *1600 columns* because my jaw is hitting the floor.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, wells.oliver@gmail.com, nunks.lol@gmail.com
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
In-Reply-To: <3C61E858-5CA7-405D-B32A-B4C89D1AC62E@elevated-dev.com>
References: <CACq6szQbQDG6_mThyH32=6J0e99-KdqOrhZMm9QwvGoVFzNbBw@mail.gmail.com> <CAOC+FBXehj4X2DMfytnPKHRWrWWZjq1G9OfUXsMop5Tex7hrvg@mail.gmail.com> <3C61E858-5CA7-405D-B32A-B4C89D1AC62E@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox