Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qd2dq-001zHN-I5 for pgsql-www@arkaria.postgresql.org; Mon, 04 Sep 2023 06:00:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qd2dp-008jXJ-Ff for pgsql-www@arkaria.postgresql.org; Mon, 04 Sep 2023 06:00:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qd2dp-008jXA-5J for pgsql-www@lists.postgresql.org; Mon, 04 Sep 2023 06:00:52 +0000 Received: from mail-pf1-x436.google.com ([2607:f8b0:4864:20::436]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qd2dl-002veF-7V for pgsql-www@lists.postgresql.org; Mon, 04 Sep 2023 06:00:52 +0000 Received: by mail-pf1-x436.google.com with SMTP id d2e1a72fcca58-68c0d886ea0so907047b3a.2 for ; Sun, 03 Sep 2023 23:00:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgug.de; s=google; t=1693807247; x=1694412047; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=s4ZwDxPVs/vKUvlDY9dDwF3vMAae3y7PConUoVHxRb4=; b=dAYbwcceVDHla7zOoPeDhLthGvTjeivyDFNm/N9O0CSFXO71TBb7MM9iMShgoxY2t4 5O5KMJqCnc2LYGIzuNbzRzsBz3bh3C/XZDyItWtiHb+OgtPFHo1v2NRR9vR48MAHu6LR 6dD7CEzfrDL0D7Ccq3q/tiI14c+reDhMDBaSKrOWpWuUsl8/46WuRN3wqFhbGAwIqR1N h3IoaePpUINK1G9wTL3JHyfWk4ct6cwUjglZd9rUNi1M9KiaZKTXyJiyiBHqr5MYIxo7 +B7o/+vkIWOPjBkQkgekg9JvRbRrwf6Iv/nFKElv7NM8RUZrPZlgH3f8sg6XFKZJ8U03 Motw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693807247; x=1694412047; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=s4ZwDxPVs/vKUvlDY9dDwF3vMAae3y7PConUoVHxRb4=; b=JMxfQ03ABos3yjk510Cbbrv+Js2ynip4+m1jzUWlfPCK6Hobk2xmwmqYFepd6XOYcN FnDCCYwyQboGsqxdxwx54HGiD9lGkuGTjPbEEtDU1euGhUMpWBUyzNEmjcQUSomWOtLx mzBOhUpQWjL+0jrwBr07eyOEGMTNxxMO047d/V58v/ms7N9e+ZhhdC46S19XNobQqW3K b3G7fsaeiRvBIRqkLONr5qda48rZYJbyTo7Y4sLmcf7HhzceRzOj9LvhpPovgQCyO+Or 7RyGPej84PmLSryV/1RqSjlN2qP8Meo60PXW5w829mKbPb2s9rmkQEv9WOONUHI1fPsT w56Q== X-Gm-Message-State: AOJu0YxkBWj7Z+Iqn9GODdUoaRbS4EcPEQvZQ973XuSuaxzhCX9qJW84 B1E0T4wxiPa1+xq9il5fhWcEfMtlpYuXjFknvMcYL5iRi62HB6IEeUg= X-Google-Smtp-Source: AGHT+IGbnNgfeHiaH4vzcijzyPG6fL2wLEh6kfWhYwaEAChn77icDpu98E0wdB+LVEMseAt9VvaUvNCOgxDTIUVvrYg= X-Received: by 2002:a05:6a20:1444:b0:10f:be0:4dce with SMTP id a4-20020a056a20144400b0010f0be04dcemr12902308pzi.8.1693807246648; Sun, 03 Sep 2023 23:00:46 -0700 (PDT) MIME-Version: 1.0 From: "Andreas 'ads' Scherbaum" Date: Mon, 4 Sep 2023 08:00:00 +0200 Message-ID: Subject: New blog - who dis? To: pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000004131030604823b4a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004131030604823b4a Content-Type: text/plain; charset="UTF-8" Hello, I plan to migrate my blog to a new software platform, which will also change the URLs which appear in the RSS feed. There is no convenient way to keep the old URLs in place. Most importantly, this will affect Planet PostgreSQL, which suddenly might see about 150 "new" blog postings. Is there a recommended way how to deal with such a move? Did someone do such a move before, what is your experience? Thanks, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project --0000000000004131030604823b4a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello,

I plan= to migrate my blog to a new software platform, which
will also c= hange the URLs which appear in the RSS feed. There
is no convenie= nt way to keep the old URLs in place.

Most imp= ortantly, this will affect Planet PostgreSQL, which
suddenly migh= t see about 150 "new" blog postings.

Is th= ere a recommended way how to deal with such a move?
Did someone do such a move before, what is your experience= ?


Thanks,

<= /div>--
<= /span>Andreas 'ads' Scherbaum
German PostgreSQL User Group
Eu= ropean PostgreSQL User Group - Board of Directors
Volunteer Regional Con= tact, Germany - PostgreSQL Project
--0000000000004131030604823b4a--