"Naik, Sameer" writes:
> On Mon, May 20, 2019 at 09:37:34PM +, Deepak Somaiya wrote:
>> wow this is interesting!
>> @Tom, Bruce, David - Experts
>> Any idea why would changing the datatype would cause so much degradation -
>> this is even when plan remains the same ,data is same.
I see nothi
Greetings,
Please don't post these kinds of questions to this list, it's not the
right list.
Pick the correct list to use in the future, and don't cross-post to
multiple lists.
This list is specifically for performance issues and questions regarding
PostgreSQL, not about how to upgrade. For tha
Hi Mariel,
On 5/23/19 1:07 PM, Mariel Cherkassky wrote:
>
>
> Hey,
>
> I upgraded the primary, then I run the rsync command in the primary :
> rsync --archive --delete --hard-links --size-only --no-inc-recursive
> /var/lib/pgsql/data /var/lib/pgsql/11/data/
> secondary_ip:/var/lib/pgsql/data/
> 2019-05-23 04:17:02 EDT 23593 DETAIL: The database cluster was initialized
> with PG_CONTROL_VERSION 960, but the server was compiled with
> PG_CONTROL_VERSION 1100.
It appears that you have not upgraded the standby server, so either use "rsync"
or simply destroy and rebuild it from scratc
Hey,
I have 2 nodes that are configured with streaming replication (PG 9.6,
repmgr 4.3).
I was trying to upgrade the nodes to PG11 with the doc -
https://www.postgresql.org/docs/11/pgupgrade.html
Everything goes well until I try to start the secondary and then it fails
on the next error :
2019-05-
@Tom, Bruce, David
>> It's generally a good idea to share explain analyze output for both versions
>> of the query - both with citext and text.
Below are the queries and explain plan output(custom plan and generic plan) for
both versions (with citext and text)
Case Insensitive -
PREPARE slowQu
