Hi Rene,
On 11/19/18 8:46 PM, Rene Romero Benavides wrote:
Not sure about the root cause but I can make these observations and
raise some questions:
1) 9.6.6 is five bug fix versions behind
Valid point to raise.
2) 300GB is so big a table, wouldn't make sense to you to partition it ?
2a) or i
On 11/19/18 11:09 PM, Laurenz Albe wrote:
With these settings, any conflicting query will be canceled after five
minutes. Perhaps your actual settings are different.
What do you get for
SELECT * FROM pg_settings WHERE name = 'max_standby_streaming_delay';
Hi Laurenz, thanks for backing up m
Martín
On Tue, Nov 20th, 2018 at 6:0 PM, Tom Lane wrote:
>
>
>
> =?UTF-8?q?Mart=C3=ADn_Fern=C3=A1ndez?= < fmarti...@gmail.com > writes:
> > First thing that generated a lot of noise in my head was the following,
> if pg assigns contiguous numeric values for the txid, how does pg deal
> with f
=?UTF-8?q?Mart=C3=ADn_Fern=C3=A1ndez?= writes:
> First thing that generated a lot of noise in my head was the following, if pg
> assigns contiguous numeric values for the txid, how does pg deal with
> fragmentation issues ? Then I later found that the txid space is actually
> circular and not l
Hello everyone, second time writing to this awesome mailing list.
I’m helping manage a postgresql 9.2.24 high volume transaction database and
yesterday we were literally one hour away of having to deal with transaction id
wraparound. We were really lucky about identifying the issue one hour befo
The devil really is in the details.
> end might be using a different timezone setting.) I'm pretty sure
> either timestamp = timestamp or timestamptz = timestamptz would be
> pushable.
Yeah, casting to plain old timestamp worked.
Thanks Tom.
Rhys
Peace & Love|Live Long & Prosper
"Rhys A.D. Stewart" writes:
> I'm using postgres_fdw and am having a pushdown issue. The TL;DR is
> that the where clause doesn't get pushed down for the last of the
> following three queries.
> SELECT * FROM service.mrrdr_synth WHERE premises = '1057430';
> SELECT * FROM service.mrrdr_synth WHER
Greetings all,
I'm using postgres_fdw and am having a pushdown issue. The TL;DR is
that the where clause doesn't get pushed down for the last of the
following three queries.
SELECT * FROM service.mrrdr_synth WHERE premises = '1057430';
SELECT * FROM service.mrrdr_synth WHERE reading_val = '8';
SE
Hello community,
We currently have a primary/standby setup and we currently need to run an
application that uses connections via ODBC.
Does somebody knows if we can with ODBC, like libpq, use a connection
string or dns entry with multiple hosts? We would like to connect
automatically to the prima
Hi,
El lun., 19 nov. 2018 a las 17:15, Chris Mair () escribió:
>
> Hi,
>
> on a CentOS 7.5 machine with PostgreSQL 10.3 installed from the PGDG yum repo,
> I have a strange error when trying to update to 10.6.
>
> A simple "yum update" updated everything except postgresql10-server.x86_64!
>
> That
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Mon, Nov 19, 2018 at 9:04 PM Stephen Frost wrote:
> > * Magnus Hagander (mag...@hagander.net) wrote:
> > > On Mon, Nov 19, 2018 at 4:01 PM Stephen Frost
> > wrote:
> > > > * Magnus Hagander (mag...@hagander.net) wrote:
> > > > > This
On Mon, Nov 19, 2018 at 9:04 PM Stephen Frost wrote:
> Greetings,
>
> * Magnus Hagander (mag...@hagander.net) wrote:
> > On Mon, Nov 19, 2018 at 4:01 PM Stephen Frost
> wrote:
> > > * Magnus Hagander (mag...@hagander.net) wrote:
> > > > This has now been pushed, so both the schedule and the sess
Hi
út 20. 11. 2018 v 8:40 odesílatel Nicklas Karlsson
napsal:
> Yes, that it surely one option but is there any grant that can be made on
> a function so that it can only be called from within the same schema? Even
> then it is a bit cumbersome
>
I have a patch, that can do it - but, probably n
13 matches
Mail list logo
