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 1uzMJM-002Yow-SV for pgsql-general@arkaria.postgresql.org; Thu, 18 Sep 2025 21:37:05 +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 1uzMJL-002DKi-Jl for pgsql-general@arkaria.postgresql.org; Thu, 18 Sep 2025 21:37:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uzMJL-002DKS-1M for pgsql-general@lists.postgresql.org; Thu, 18 Sep 2025 21:37:03 +0000 Received: from mail-pl1-x634.google.com ([2607:f8b0:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uzMJI-0019sL-2K for pgsql-general@lists.postgresql.org; Thu, 18 Sep 2025 21:37:02 +0000 Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-269ba651d06so605405ad.0 for ; Thu, 18 Sep 2025 14:37:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758231420; x=1758836220; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fljmfOWPT9isKxM3lbPIX5jZpAaix6pvy8kDsodu5f0=; b=byB9To1+qJzBtxZqrqmbJxmEAvrsDVTxUsSX/VF7pbzTu2IR2HYF+SMuDyuRQgnz/z cBJGkLc4fDaLFx1PXV8xRLUdFTSfPQRpXfqSZLnFtkM5W3iauYazmvIQ3daW7zGnTGY6 PYxb1vdjy/D/Vk43h48R9YcjsrzEkuI0bA2lcGtOUwB1JfCT0CA7j0uF4AGCyknixQh6 iAZDRLu3BdABmMXLyxPtkE2pClvpmE3Zx2FG0kz7jrw4tXXepgJkMil9DKs5Nj4+0iks 4jiKll4QXC6/9uOjxonGhHS03NS+5JqhbZs+W1PsuY/O/7UMN1OxbPCwskclWME1kfuV 0gug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758231420; x=1758836220; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fljmfOWPT9isKxM3lbPIX5jZpAaix6pvy8kDsodu5f0=; b=vRbhX8J3YovudI6WKqTRyriWtR3xm2eMEJdJQkU6Q+x7DLsAdwnYEDf0+lRXdYRpF3 n9bI196aYCE6QK+F92gkVILskj7Osi9zdUKtHq8YTzLRj/q1iY2ShVNHRl+bvzEWkV51 UsjUU+c/i4PVMooMdROiTfBQ9PsB06urpH+Po7Y99J6HSRq6r2AjolBib9QGJrorF7rS zDRePDVL8hReNyi+6AqkxmdPPpj/CYUNrKSvgPdJ9To7CWyb6prrYZ2ArZ9GI2xu2HGN GcKvW8E78/NkUrYB/6lVnfVkg5OC0gtQ/dYiXnJXxuWfeZCq1z8KsQQjXq4kc1mmSFID e8pw== X-Forwarded-Encrypted: i=1; AJvYcCXvARBNHm0BPb5SqAJO23hf5u9EhyNM94AVym8V2W4KtoqtIEwoyKMn96FcLzCL6FT5GRWpJQlrlccmT6oR@lists.postgresql.org X-Gm-Message-State: AOJu0YwraN8E8gPavukhvCPx/N2CAamQ2CUm/uVpCaavMZNpsyl4i+0I yCnG51zuraqtLxh8gAbZ548Kfzkx5kXDxjv10/jvdENL9bnwADfHxn/PbzxYvgRr7YLS6VNqIUM bMcREaomUxGgFLUxYyP7KieM3hOc2TWs= X-Gm-Gg: ASbGnctcMJVlvQorFj113v/BSNBmkPU6E7CbHQ0K+fdZzfp8SM/3+0FWgl9L36iRifc cfDL21JwiYBoy7FSJS3fvEO2Mid0ZPU7vRuhS/b5+KCnN2r4aq7MvgwB2RQhq4yfQDOdisGNLut uwhTDMpBOYQ1U6HIMXwzfUJBFyoOvyNwXF7Zm79NHmPIqo6B7/l5xjYsre9H/QPSFBay+0xXSaB wUiXpcT20+6JkDHRM1AFRBGKUlnQk7qOApU8P2H X-Google-Smtp-Source: AGHT+IHRjBxw128tX07f0/k0un9LtBbIKwOCZGCE81VD3dmu/7ld1BjTnG1XkGEtuZ5qNiKm1TINKNZWFibXAZeJ0Ks= X-Received: by 2002:a17:902:8f90:b0:269:85aa:3776 with SMTP id d9443c01a7336-269ba565f84mr5201445ad.11.1758231419896; Thu, 18 Sep 2025 14:36:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: R Wahyudi Date: Fri, 19 Sep 2025 07:36:46 +1000 X-Gm-Features: AS18NWCkOYFTDxEx2PCiGPBo8R91LC0NvcDFS7JwsfQFOoSERaVi5mscI3nBvfs Message-ID: Subject: Re: pg_restore scan To: Adrian Klaver Cc: Ron Johnson , "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000003749cf063f1a275f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003749cf063f1a275f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I've been given a database dump file daily and I've been asked to restore it. I tried everything I could to speed up the process, including using -j 40. I discovered that at the later stage of the restore process, the following behaviour repeated a few times : 40 x pg_restore process doing 100% CPU 40 x postgres process doing COPY but using 0% CPU ..... and zero disk write activity I don't see this behaviour when restoring the database that was dumped with -Fd. Also with an un-piped backup file, I can restore a specific table without having to wait for hours. -- On Fri, 19 Sept 2025 at 01:54, Adrian Klaver wrote: > On 9/18/25 05:58, R Wahyudi wrote: > > Hi All, > > > > Thanks for the quick and accurate response! I never been so happy > > seeing IOwait on my system! > > Because? > > What did you find? > > > > > I might be blind as I can't find information about 'offset' in pg_dump > > documentation. > > Where can I find more info about this? > > It is not in the user documentation. > > From the thread Ron referred to, there is an explanation here: > > https://www.postgresql.org/message-id/366773.1756749256%40sss.pgh.pa.us > > I believe the actual code, for the -Fc format, is in pg_backup_custom.c > here: > > > https://github.com/postgres/postgres/blob/master/src/bin/pg_dump/pg_backu= p_custom.c#L723 > > Per comment at line 755: > > " > If possible, re-write the TOC in order to update the data offset > information. This is not essential, as pg_restore can cope in most > cases without it; but it can make pg_restore significantly faster > in some situations (especially parallel restore). We can skip this > step if we're not dumping any data; there are no offsets to update > in that case. > " > > > > > Regards, > > Rianto > > > > On Wed, 17 Sept 2025 at 13:48, Ron Johnson > > wrote: > > > > > > PG 17 has integrated zstd compression, while --format=3Ddirectory l= ets > > you do multi-threaded dumps. That's much faster than a single- > > threaded pg_dump into a multi-threaded compression program. > > > > (If for _Reasons_ you require a single-file backup, then tar the > > directory of compressed files using the --remove-files option.) > > > > On Tue, Sep 16, 2025 at 10:50=E2=80=AFPM R Wahyudi > > wrote: > > > > Sorry for not including the full command - yes , its piping to = a > > compression command : > > | lbzip2 -n --best > > > > > > > I think we found the issue! I'll do further testing and see how > > it goes ! > > > > > > > > > > > > On Wed, 17 Sept 2025 at 11:02, Ron Johnson > > > > wrote: > > > > So, piping or redirecting to a file? If so, then that's th= e > > problem. > > > > pg_dump directly to a file puts file offsets in the TOC. > > > > This how I do custom dumps: > > cd $BackupDir > > pg_dump -Fc --compress=3Dzstd:long -v -d${db} -f ${db}.dump > > 2> ${db}.log > > > > On Tue, Sep 16, 2025 at 8:54=E2=80=AFPM R Wahyudi > > > wrote: > > > > pg_dump was done using the following command : > > pg_dump -Fc -Z 0 -h -U -w -d > > > > On Wed, 17 Sept 2025 at 08:36, Adrian Klaver > > > > wrote: > > > > On 9/16/25 15:25, R Wahyudi wrote: > > > > > > I'm trying to troubleshoot the slowness issue > > with pg_restore and > > > stumbled across a recent post about pg_restore > > scanning the whole file : > > > > > > > "scanning happens in a very inefficient way, > > with many seek calls and > > > small block reads. Try strace to see them. This > > initial phase can take > > > hours in a huge dump file, before even starting > > any actual restoration." > > > see : https://www.postgresql.org/message-id/ > > E48B611D-7D61-4575-A820- > > www.postgresql.org/message-id/E48B611D-7D61-4575-A820-> > > > B2C3EC2E0551%40gmx.net > > > www.postgresql.org/message-id/> > > > E48B611D-7D61-4575-A820-B2C3EC2E0551%40gmx.net > > > > > > > This was for pg_dump output that was streamed to a > > Borg archive and as > > result had no object offsets in the TOC. > > > > How are you doing your pg_dump? > > > > > > > > -- > > Adrian Klaver > > adrian.klaver@aklaver.com > > > > > > > > > > -- > > Death to , and butter sauce. > > Don't boil me, I'm still alive. > > lobster! > > > > > > > > -- > > Death to , and butter sauce. > > Don't boil me, I'm still alive. > > lobster! > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > --0000000000003749cf063f1a275f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've been given a database dump file dai= ly and I've been asked to restore it.=C2=A0
I tried = everything I could to speed up the process, including using -j 40.=C2=A0

I discovered that at the later sta= ge of the restore process,=C2=A0 the following=C2=A0behaviour repeated a fe= w times :=C2=A0
40 x pg_restore process doing 100% CPU
40 x=C2=A0 postgres process doing COPY but using 0% CPU= =C2=A0
..... and zero disk write activity

I don't see this behaviour when restoring = the database that was dumped with -Fd.
Also with an un-p= iped backup file, I can restore a specific table without having to wait for= hours.=C2=A0


--





On Fri, 19 Sept 20= 25 at 01:54, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 9/18/25 05:58, R Wahyudi wrote:
> Hi All,
>
> Thanks for the quick and accurate response!=C2=A0 I never been so happ= y
> seeing IOwait on my system!

Because?

What did you find?

>
> I might be blind as=C2=A0 I can't find information about 'offs= et' in pg_dump
> documentation.
> Where can I find more info about this?

It is not in the user documentation.

=C2=A0From the thread Ron referred to, there is an explanation here:

https://www.postgresql.org/me= ssage-id/366773.1756749256%40sss.pgh.pa.us

I believe the actual code, for the -Fc format, is in pg_backup_custom.c here:

https://gith= ub.com/postgres/postgres/blob/master/src/bin/pg_dump/pg_backup_custom.c#L72= 3

Per comment at line 755:

"
=C2=A0 If possible, re-write the TOC in order to update the data offset information.=C2=A0 This is not essential, as pg_restore can cope in most cases without it; but it can make pg_restore significantly faster
in some situations (especially parallel restore).=C2=A0 We can skip this step if we're not dumping any data; there are no offsets to update
in that case.
"

>
> Regards,
> Rianto
>
> On Wed, 17 Sept 2025 at 13:48, Ron Johnson <ronljohnsonjr@gmail.com
> <mailto:ronljohnsonjr@gmail.com>> wrote:
>
>
>=C2=A0 =C2=A0 =C2=A0PG 17 has integrated zstd compression, while --form= at=3Ddirectory lets
>=C2=A0 =C2=A0 =C2=A0you do multi-threaded dumps.=C2=A0 That's much = faster than a single-
>=C2=A0 =C2=A0 =C2=A0threaded pg_dump into a multi-threaded compression = program.
>
>=C2=A0 =C2=A0 =C2=A0(If for _Reasons_ you require a single-file backup,= then tar the
>=C2=A0 =C2=A0 =C2=A0directory of compressed files using the=C2=A0--remo= ve-files option.)
>
>=C2=A0 =C2=A0 =C2=A0On Tue, Sep 16, 2025 at 10:50=E2=80=AFPM R Wahyudi = <rwahyudi@gmail.= com
>=C2=A0 =C2=A0 =C2=A0<mailto:rwahyudi@gmail.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sorry for not including the full comm= and - yes , its piping to a
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0compression command :
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| lbzip2 -n <threadsforbzip= goeshere>--best > <filenamegoeshere>
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I think=C2=A0we found the issue! I= 9;ll do further testing and see how
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0it goes !
>
>
>
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Wed, 17 Sept 2025 at 11:02, Ron Jo= hnson
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<ronljohnsonjr@gmail.com <mailto:ronljohnsonjr@gmail.c= om>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0So, piping or redirecti= ng to a file?=C2=A0 If so, then that's the
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0problem.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pg_dump directly to a f= ile puts file offsets in the TOC.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This how I do custom du= mps:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd $BackupDir
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pg_dump -Fc --compress= =3Dzstd:long -v -d${db} -f ${db}.dump
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02> ${db}.log<= br> >
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Tue, Sep 16, 2025 at= 8:54=E2=80=AFPM R Wahyudi
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<rwahyudi@gmail.com <mailto:rwahyudi@gmail.com&= gt;> wrote:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pg_dump w= as done using the following command :
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pg_dump -= Fc -Z 0 -h <host> -U <user> -w -d <database>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Wed, 1= 7 Sept 2025 at 08:36, Adrian Klaver
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<adrian.klaver@akl= aver.com
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<mailt= o:adrian.kla= ver@aklaver.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0On 9/16/25 15:25, R Wahyudi wrote:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > I'm trying to troubleshoot the slowness issue
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0with pg_restore and
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > stumbled across a recent post about pg_restore
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0scanning the whole file :
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 >=C2=A0 > "scanning happens in a very inefficient way, >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0with many seek calls and
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > small block reads. Try strace to see them. This
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0initial phase can take
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > hours in a huge dump file, before even starting
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0any actual restoration."
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > see : https://www.postgresql.org/message-id/ >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0E48B611D-7D61-4575-A820- <https://
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0www.postgresql.org/message-id/E48= B611D-7D61-4575-A820->
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > B2C3EC2E0551%40gmx.net <http://40gmx.net>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0<https://www.postgresql.org/message-id/ <https= ://
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0www.postgresql.org/message-id/>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 > E48B611D-7D61-4575-A820-B2C3EC2E0551%40gmx.net
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0<http://40gmx.net>>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0This was for pg_dump output that was streamed to a
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Borg archive and as
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0result had no object offsets in the TOC.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0How are you doing your pg_dump?
>
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0--
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Adrian Klaver
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0adrian= .klaver@aklaver.com
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0<mailto:adrian.klaver@aklaver.com>
>
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Death to <Redacted&g= t;, and butter sauce.
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Don't boil me, I= 9;m still alive.
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<Redacted> lobste= r!
>
>
>
>=C2=A0 =C2=A0 =C2=A0--
>=C2=A0 =C2=A0 =C2=A0Death to <Redacted>, and butter sauce.
>=C2=A0 =C2=A0 =C2=A0Don't boil me, I'm still alive.
>=C2=A0 =C2=A0 =C2=A0<Redacted> lobster!
>


--
Adrian Klaver
adrian.klave= r@aklaver.com
--0000000000003749cf063f1a275f--