Hi Rama,
On 02/10/2020 01:42, Rama Krishnan wrote:
> Hi Friends,
>
> By using pg bouncer can we split read and queries
>
pgbouncer is just a connection pooler.
The logic where to send the reads and where the writes, should be in our
application.
regards,
fabio pardi
Yeah. Rob
On Fri, 2 Oct, 2020, 05:14 Rob Sargent, wrote:
>
>
> > On Oct 1, 2020, at 5:42 PM, Rama Krishnan wrote:
> >
> > Hi Friends,
> >
> > By using pg bouncer can we split read and queries
> >
> > Thank
> > Rk
>
> Did you mean reads vs writes?
>
Yeah rob can we spilt read/write queries using pgbouncer
On Fri, 2 Oct, 2020, 08:43 Rama Krishnan, wrote:
> Yeah. Rob
>
> On Fri, 2 Oct, 2020, 05:14 Rob Sargent, wrote:
>
>>
>>
>> > On Oct 1, 2020, at 5:42 PM, Rama Krishnan wrote:
>> >
>> > Hi Friends,
>> >
>> > By using pg bouncer can we sp
On 10/1/20 4:08 PM, tutilu...@tutanota.com wrote:
Yeah, this isn't rude or insulting at all...
It would be refreshing to hear your be honest for once and just admit
that you *want* it to be difficult. You *like* that there's a high
threshold and it makes you feel superior to exclude "dum
On Wed, Sep 30, 2020 at 7:41 AM Tom Lane wrote:
> If you really really need to do this, I'd counsel using EXECUTE to
> ensure no caching happens. But I concur with Michael that it's
> fundamentally a bad idea.
>
Agreed, though the documentation seems a bit loose here. The fact that the
temp ta
> On Oct 1, 2020, at 5:42 PM, Rama Krishnan wrote:
>
> Hi Friends,
>
> By using pg bouncer can we split read and queries
>
> Thank
> Rk
Did you mean reads vs writes?
Hi Friends,
By using pg bouncer can we split read and queries
Thank
Rk
> On Oct 1, 2020, at 16:08, tutilu...@tutanota.com wrote:
> But of course I should be grateful no matter what because it doesn't cost
> money.
No one is asking you to be grateful. However, you are asking for other people
to do things that important to you, but not them. They are not require
> On Thu, Sep 24, 2020 at 10:40 PM <> tutilu...@tutanota.com> > wrote:
>
>>
>>
>>> Well not partial as in incremental. Instead dump only some portion of the
>>> schema with or without its associated data.
>>>
>> It's funny that you should bring that up, considering how it was one of my
>> poin
On Thu, Oct 1, 2020 at 2:02 PM David G. Johnston
wrote:
> The convention on these lists is to inline or bottom-post, please do not
> top-post.
>
> On Thu, Oct 1, 2020 at 10:41 AM Jonathan Strong
> wrote:
>
>> I've been away from coding for several years, but dusting off my chops
>> and getting b
The convention on these lists is to inline or bottom-post, please do not
top-post.
On Thu, Oct 1, 2020 at 10:41 AM Jonathan Strong
wrote:
> I've been away from coding for several years, but dusting off my chops and
> getting back up to speed with PostgreSQL (love it!). So please forgive me
> if
I've been away from coding for several years, but dusting off my chops and
getting back up to speed with PostgreSQL (love it!). So please forgive me
if my early answers here come off as naive. But my understanding of this
suggests that you shouldn't be using "update" on a serial field. I'm
guessing
On Thu, Oct 1, 2020 at 09:03:31AM -0700, Adrian Klaver wrote:
> On 10/1/20 7:51 AM, Sean Brown wrote:
> > I’m having a little problem using pg_upgrade to move from 10 to 13, I’m
> > assuming the issue is related to the removal of pg_pltemplate, but I can’t
> > find anything related to how to han
Hi developers,
We have a strange case where some rows are removed. I think it is a bug,
but before notifying it I prefer to ask here where I am wrong.
*Postgres 12*
Given the following structure:
create table parent ( id serial, constraint parent_pkey primary key (id))
partition by range (id);
cr
On 10/1/20 7:51 AM, Sean Brown wrote:
I’m having a little problem using pg_upgrade to move from 10 to 13, I’m
assuming the issue is related to the removal of pg_pltemplate, but I can’t find
anything related to how to handle it.
pg_upgrade —check reports that the clusters are compatible, but th
On Thu, Oct 1, 2020 at 05:28:53PM +0200, Thomas Kellerer wrote:
>
>
> Sean Brown schrieb am 01.10.2020 um 16:51:
> > I’m having a little problem using pg_upgrade to move from 10 to 13,
> > I’m assuming the issue is related to the removal of pg_pltemplate,
> > but I can’t find anything related to
Sean Brown schrieb am 01.10.2020 um 16:51:
I’m having a little problem using pg_upgrade to move from 10 to 13,
I’m assuming the issue is related to the removal of pg_pltemplate,
but I can’t find anything related to how to handle it.
pg_upgrade —check reports that the clusters are compatible,
I’m having a little problem using pg_upgrade to move from 10 to 13, I’m
assuming the issue is related to the removal of pg_pltemplate, but I can’t find
anything related to how to handle it.
pg_upgrade —check reports that the clusters are compatible, but the actual
upgrade fails starting the new
"Srinivasa T N" wrote on 01/10/2020 11:47:33:
> On Thu, Oct 1, 2020 at 2:47 PM Alban Hertroys <
> alban.hertr...@apollovredestein.com> wrote:
> Hi all,
>
> We're seeing the FATAL error message from the subject pop up in our
> logs at regular intervals, but I haven't been able to pinpoint what
On Thu, Oct 1, 2020 at 2:47 PM Alban Hertroys <
alban.hertr...@apollovredestein.com> wrote:
> Hi all,
>
> We're seeing the FATAL error message from the subject pop up in our logs
> at regular intervals, but I haven't been able to pinpoint what is causing
> it. I'm hoping for some insights here.
>
Hi all,
We're seeing the FATAL error message from the subject pop up in our logs
at regular intervals, but I haven't been able to pinpoint what is causing
it. I'm hoping for some insights here.
We run a PostgreSQL 11.9 server on CentOS 7, within a vmware environment:
PostgreSQL 11.9 on x86_64-
21 matches
Mail list logo
