On 4/3/19 12:44 PM, Reindl Harald wrote:
beasue any application which can't read it's data after upgrade to a new
version is f**g crap and pretty unusable when using as example
distro-packages - when you forgot the dump with the old version your are
fucked
That explains.
Thank you.
MJ
Am 03.04.19 um 09:54 schrieb mj:
> On 3/28/19 11:59 AM, Reindl Harald wrote:
>> our production datadirs date back to 2002, originally on windows then
>> moved to MacOS and in 2008 to Fedora and i did not dump/restore a single
>> time in my whole life, this is not postgresql
>
> Just curiosity:
On 4/3/19 10:23 AM, Vincent Hoffman-Kazlauskas wrote:
PostgreSQL until relatively recently (8.something) required you to dump
and restore all your data for a major version upgrade. For some people
this was an argument against using PostgreSQL.
Ah,thanks! Didn't know that.
MJ
__
On 03/04/2019 08:54, mj wrote:
> Hi,
>
> On 3/28/19 11:59 AM, Reindl Harald wrote:
>> our production datadirs date back to 2002, originally on windows then
>> moved to MacOS and in 2008 to Fedora and i did not dump/restore a single
>> time in my whole life, this is not postgresql
>
> Just curio
Hi,
On 3/28/19 11:59 AM, Reindl Harald wrote:
our production datadirs date back to 2002, originally on windows then
moved to MacOS and in 2008 to Fedora and i did not dump/restore a single
time in my whole life, this is not postgresql
Just curiosity: does the above statement mean that you cons
On Thu, Mar 28, 2019 at 11:16 AM Michal Schorm wrote:
>
> Hello,
> I have a questions regarding the warnings showing up at 10.2 and 10.3
> releases:
>
> When upgrading from MariaDB 10.2.16 or earlier to MariaDB 10.2.17 or higher,
> running mysql_upgrade is required due to changes introduced in MD
Am 28.03.19 um 11:16 schrieb Michal Schorm:
> Hello,
> I have a questions regarding the warnings showing up at 10.2 and 10.3
> releases:
>
> When upgrading from MariaDB 10.2.16 or earlier to MariaDB 10.2.17 or higher,
> running mysql_upgrade is required due to changes introduced in MDEV-14637.
Hello,
I have a questions regarding the warnings showing up at 10.2 and 10.3 releases:
When upgrading from MariaDB 10.2.16 or earlier to MariaDB 10.2.17 or higher,
running mysql_upgrade is required due to changes introduced in MDEV-14637.
When upgrading from MariaDB 10.3.8 or earlier to MariaDB 1
8 matches
Mail list logo
