bhargav kamineni wrote:
> Hi Team,
>
> I have configured replication using slot ,But it failed by throwing the
> ERROR pg_basebackup: could not get transaction log end position from server:
> ERROR: requested WAL segment 00012C9D0085 has already been
> removed ,
> which is unexpec
On 28/9/18 9:00 π.μ., bhargav kamineni wrote:
Hi Team,
I have configured replication using slot ,But it failed by throwing the ERROR /pg_basebackup: could not get transaction log end position from server: ERROR: requested WAL segment
00012C9D0085 has already been removed /, which i
Thanks for the prompt response.
On Fri 28 Sep, 2018, 10:55 AM Michael Paquier, wrote:
> On Fri, Sep 28, 2018 at 10:33:30AM +0530, Raghavendra Rao J S V wrote:
> > Log file will be generated in *csv* format at *pg_log* directory in our
> > PostgreSQL. Every day we are getting one log file. We wou
Hi Team,
I have configured replication using slot ,But it failed by throwing the
ERROR *pg_basebackup: could not get transaction log end position from
server: ERROR: requested WAL segment 00012C9D0085 has already
been removed *, which is unexpected because i have created the slot on
On Fri, Sep 28, 2018 at 10:33:30AM +0530, Raghavendra Rao J S V wrote:
> Log file will be generated in *csv* format at *pg_log* directory in our
> PostgreSQL. Every day we are getting one log file. We would like to
> maintain only max 30 days. Which setting need to modify by us in
> “postgresql.con
Rob Sargent wrote:
> > Christoph Moench-Tegeder wrote:
> > > ## Laurenz Albe (laurenz.a...@cybertec.at):
> > >
> > > > vm.overcommit_memory = 2
> > > > vm_overcommit_ratio = 100
> > > >
> > > > Linux commits (swap * overcommit_ratio * RAM / 100),
> > >
> > > ^
> > >
Hi All,
Log file will be generated in *csv* format at *pg_log* directory in our
PostgreSQL. Every day we are getting one log file. We would like to
maintain only max 30 days. Which setting need to modify by us in
“postgresql.conf” in order to recycle the log files after 30 days.
--
Regards,
Ragha
> On Sep 27, 2018, at 3:45 PM, Laurenz Albe wrote:
>
> Christoph Moench-Tegeder wrote:
>> ## Laurenz Albe (laurenz.a...@cybertec.at):
>>
>>> vm.overcommit_memory = 2
>>> vm_overcommit_ratio = 100
>>>
>>> Linux commits (swap * overcommit_ratio * RAM / 100),
>>
>> ^
>>
Jan Kowalski writes:
> I've strange problem with Pyramid application working with postgresql
> over psycopg2.
> After some period of operation, my application insert new row to one of
> tables with the message:
> ERROR: permission denied for relation ...
> After restart of application, it starts
Hello!
I've strange problem with Pyramid application working with postgresql
over psycopg2.
After some period of operation, my application insert new row to one of
tables with the message:
ERROR: permission denied for relation ...
After restart of application, it starts to work properly again.
Christoph Moench-Tegeder wrote:
> ## Laurenz Albe (laurenz.a...@cybertec.at):
>
> > vm.overcommit_memory = 2
> > vm_overcommit_ratio = 100
> >
> > Linux commits (swap * overcommit_ratio * RAM / 100),
>
> ^
> That should be a "+".
Yes; shame on me for
Deepti Sharma S wrote:
> Can you please confirm if PostgreSQL version 9.4.x is compatible with RHEL7.5?
Yes; there are even PGDG binaries on
https://www.postgresql.org/download/linux/redhat/:
yum install
https://download.postgresql.org/pub/repos/yum/9.4/redhat/rhel-7-x86_64/pgdg-redhat94-9.4-3.
Many thanks, sorry for missing something so obvious!
On Thu, Sep 27, 2018 at 1:45 PM, Tom Lane wrote:
> Charles Leifer writes:
> > I'm running into behavior I don't understand when trying to do an UPSERT
> > with Postgres. The docs would seem to indicate that the conflict target
> of
> > the IN
Charles Leifer writes:
> I'm running into behavior I don't understand when trying to do an UPSERT
> with Postgres. The docs would seem to indicate that the conflict target of
> the INSERT statement can be either an index expression or a constraint
> name. However, when attempting to reference the
Hi,
I'm running into behavior I don't understand when trying to do an UPSERT
with Postgres. The docs would seem to indicate that the conflict target of
the INSERT statement can be either an index expression or a constraint
name. However, when attempting to reference the constraint name, I get a
"c
Greetings,
* Ravi Krishna (srkrish...@aol.com) wrote:
> Is there a place to get all PG related security alerts? I saw this in IBM
> site:
https://www.postgresql.org/support/security/
Thanks!
Stephen
signature.asc
Description: PGP signature
Hi
Is there a place to get all PG related security alerts? I saw this in IBM site:
https://www-01.ibm.com/support/docview.wss?uid=ibm10730491
which points to this:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10915
>From the looks of it, it seems to be a generic libpq
Hi Team,
Can you please confirm if PostgreSQL version 9.4.x is compatible with RHEL7.5?
DEEPTI SHARMA
Specialist
ITIL 2011 Foundation Certified
BDGS, R&D
Ericsson
3rd Floor, ASF Insignia - Block B Kings Canyon,
Gwal Pahari, Gurgaon, Haryana 122 003, India
Phone 0124-6243000
deepti.s.sha...@e
18 matches
Mail list logo
