Rakesh,
As long as one application knows how to connect to more than 1 tenant,
there will *always* be the possibility that a software bug in your
application causes one tenant to access another tenant's data. I think this
is why you're getting people asking you to refine your requirements. There
q
ollisions on their created_at timestamp?
Thanks!
Colin
On Thu, Sep 29, 2016 at 7:09 PM Guyren Howe wrote:
> On Sep 29, 2016, at 16:03 , Colin Morelli wrote:
> >
> > Hey list,
> >
> > I'm using UUID primary keys in my application. I need to add pagination,
> and am
Hey list,
I'm using UUID primary keys in my application. I need to add pagination,
and am trying to avoid OFFSET/LIMIT. I do have a created_at timestamp that
I could use, but it's possible for multiple records to be created at the
same timestamp (postgres offers millisecond precision here, I belie
0 the next scheduled release after 9.6 - so next
year?). If so, I'd greatly appreciate any more info you have on the new
design (even patches if you have them).
Best,
Colin
On Wed, Aug 10, 2016 at 12:53 AM Simon Riggs wrote:
> On 6 August 2016 at 04:17, Colin Morelli wrote:
>
>
plication never sees the event at LSN 3. In fact, I'm not
even sure how I could manually do this.
Hopefully that makes more sense.
Best,
Colin
On Mon, Aug 8, 2016 at 10:47 PM Venkata Balaji N wrote:
> On Sun, Aug 7, 2016 at 9:29 PM, Colin Morelli
> wrote:
>
>> Venkata,
&
at, Aug 6, 2016 at 1:17 PM, Colin Morelli
> wrote:
>
>> Hey all,
>>
>> I'm using logical decoding in my application to capture change streams
>> and ship them to Kafka. However, logical replication slots aren't included
>> in the WAL and thus don
Hey all,
I'm using logical decoding in my application to capture change streams and
ship them to Kafka. However, logical replication slots aren't included in
the WAL and thus don't make it to replicas. In the case of a failover, it's
not clear what (if anything) can be done to continue receiving a
