On Sat, Nov 25, 2017 at 8:54 PM, Dmitry Shalashov wrote:
> Is it completely safe to use manually patched version in production?
Patching upstream PostgreSQL to fix a critical bug is something that
can of course be done. And to reach a state where you think something
is safe to use in production f
On Tue, Jan 09, 2018 at 01:53:14PM -0300, Claudio Freire wrote:
> That shows 50% of that are full page writes. This is with compression
> enabled. WAL compression will only help FPW, so if you don't have a large
> volume of FPW, or they don't compress well, you won't benefit much.
This highly depe
On Tue, Jan 16, 2018 at 09:18:25PM -0800, Jeff Janes wrote:
> Oh. I've not seen that before. But then again I don't often restart my
> server and then immediately run very large queries with a stringent time
> deadline.
>
> You can try pg_prewarm, on pg_statistic table and its index. But I'd
>
On Tue, Jan 23, 2018 at 10:54:01PM -0700, pavan95 wrote:
> If you are finding some sessions then of course your database is
> perfectly alright. As sessions won't consume any memory.
Those have a cost as well when building transaction snapshots. Too much
of them is no good either, let's not forg
On Wed, Mar 14, 2018 at 02:12:47PM +0800, 彭昱傑 wrote:
> It's useful information for me.
Once archived, there is no need to keep them in the data folder as if
needed at recovery the startup process would look for timeline history
files where necessary if it needs to do a timeline jump.
> I will exa
On Fri, Mar 23, 2018 at 01:29:35PM +0530, Akshay Ballarpure wrote:
> I have a query on DB corruption. Is there any way to recover from it
> without losing data ?
Corrupted pages which need to be zeroed in order to recover the rest is
data lost forever, except if you have a backup you can rollback
On Tue, May 31, 2022 at 08:42:06AM -0700, David G. Johnston wrote:
> Building indexes is so IO heavy that the non-IO bottlenecks that exists
> likely have minimal impact on the overall times this rebuild everything
> will take. That said, I’ve never done anything at this scale before. I
> wouldn’
On Mon, Dec 04, 2023 at 09:57:24AM -0500, Tom Lane wrote:
> Jerry Brenner writes:
>> Both Oracle and SQL Server have
>> consistent hash values for query plans and that makes it easy to identify
>> when there are multiple plans for the same query. Does that concept exist
>> in later releases of Po
On Tue, Oct 30, 2018 at 11:03:14AM -0700, Joshua D. Drake wrote:
> On 10/30/18 10:51 AM, MichaelDBA wrote:
>> I am using pgadmin4 version 3.4 with PG 11.0 and I get this error when I
>> try to connect with scram authorization:
>>
>> User "myuser" does not have a valid SCRAM verifier.
>>
>> How do
On Fri, Jun 14, 2019 at 03:46:30PM +0200, Fabio Pardi wrote:
> Maybe of some interest for the past, present and future community, I
> benchmarked the impact of wal_log_hints with and without wal_compression
> enabled.
pgbench data is rather compressible per the format of its attributes,
hence I am
On Tue, Jan 14, 2020 at 04:29:51PM +0100, Joao Junior wrote:
> I would like to know if increasing the amount of shared-buffers could help
> the startup process applying the wals. I would like to know if in
> the process of reading the wals and applying them, blocks that should be
> written will b
On Wed, Jun 16, 2021 at 09:25:37PM +0500, Haseeb Khan wrote:
> Would be highly appreciated, if someone could tell me what exactly the
> issue is or what I am missing in the configuration on both the servers
> (master- slave).Why replication is not working?
Your issue is partially here, as recovery
12 matches
Mail list logo
