Re: Unable to compile postgres 13.1 on Slackware current x64

[Laurenz Albe]

On Mon, 2020-11-16 at 09:15 +0200, Condor wrote:
> unable to compile Postgresql 13.0 and 13.1 on Slackware current x64. 
> Here is gcc -v:
> 
> Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/9.3.0/specs
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-slackware-linux/9.3.0/lto-wrapper
> Target: x86_64-slackware-linux
> Configured with: ../configure --prefix=/usr --libdir=/usr/lib64 
> --mandir=/usr/man --infodir=/usr/info --enable-shared --enable-bootstrap 
> --enable-languages=ada,brig,c,c++,d,fortran,go,lto,objc,obj-c++ 
> --enable-threads=posix --enable-checking=release --enable-objc-gc 
> --with-system-zlib --enable-libstdcxx-dual-abi 
> --with-default-libstdcxx-abi=new --disable-libstdcxx-pch 
> --disable-libunwind-exceptions --enable-__cxa_atexit --disable-libssp 
> --enable-gnu-unique-object --enable-plugin --enable-lto 
> --disable-install-libiberty --disable-werror --with-gnu-ld --with-isl 
> --verbose --with-arch-directory=amd64 --disable-gtktest 
> --enable-clocale=gnu --disable-multilib --target=x86_64-slackware-linux 
> --build=x86_64-slackware-linux --host=x86_64-slackware-linux
> Thread model: posix
> gcc version 9.3.0 (GCC)
> 
> 
> ICU version - 68.1, LLVM version - 11.0.0
> 
> 
> Here is configure params:
> ./configure \
>--prefix=/usr/lib$LIBDIRSUFFIX/postgresql/$VER \
>--libdir=/usr/lib$LIBDIRSUFFIX/postgresql/$VER/lib \
>--includedir=/usr/include \
>--sysconfdir=/etc/postgresql \
>--localstatedir=/var/lib/postgresql \
>--with-tcl \
>--with-tclconfig=/usr/lib$LIBDIRSUFFIX \
>--with-perl \
>--with-python \
>--with-openssl \
>--with-libxml \
>--with-libxslt \
>--with-icu \
>--with-llvm \
>--enable-thread-safety \
>--with-system-tzdata=/usr/share/zoneinfo \
>$ARCH-slackware-linux
> 
> The error is:
> 
> make[2]: Leaving directory '/tmp/postgresql-13.1/src/backend/utils'
> make[1]: Leaving directory '/tmp/postgresql-13.1/src/backend'
> x86_64-slackware-linux-gcc -Wall -Wmissing-prototypes -Wpointer-arith 
> -Wdeclaration-after-statement -Werror=vla -Wendif-labels 
> -Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wformat-security 
> -fno-strict-aliasing -fwrapv -fexcess-precision=standard 
> -Wno-format-truncation -Wno-stringop-truncation -O2 
> -I../../../src/include  -D_GNU_SOURCE -I/usr/include/libxml2   -c -o 
> collationcmds.o collationcmds.c
> collationcmds.c: In function ‘get_icu_language_tag’:
> collationcmds.c:467:51: error: ‘TRUE’ undeclared (first use in this 
> function); did you mean ‘IS_TRUE’?
>467 |  uloc_toLanguageTag(localename, buf, sizeof(buf), TRUE, &status);
>|   ^~~~
>|   IS_TRUE
> 
> collationcmds.c:467:51: note: each undeclared identifier is reported 
> only once for each function it appears in
> make: *** [: collationcmds.o] Error 1
> 
> Changing TRUE to IS_TRUE solve the problem and code is compiled but no 
> idea is this a real fix.

"UBool" and "TRUE" are defined in "umachine.h", which is a header file for the
"libicu" library.

PostgreSQL includes "unicode/ucol.h", which will include "umachine.h"
(via "utypes.h"), so that should be fine.

Are your libicu headers installed under /usr/include/unicode?
Do you get any messages about missing include files earlier?

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com

Re: Unable to compile postgres 13.1 on Slackware current x64

[Thomas Munro]

On Mon, Nov 16, 2020 at 10:10 PM Laurenz Albe  wrote:
> On Mon, 2020-11-16 at 09:15 +0200, Condor wrote:
> > collationcmds.c: In function ‘get_icu_language_tag’:
> > collationcmds.c:467:51: error: ‘TRUE’ undeclared (first use in this
> > function); did you mean ‘IS_TRUE’?
> >467 |  uloc_toLanguageTag(localename, buf, sizeof(buf), TRUE, &status);
> >|   ^~~~
> >|   IS_TRUE
> >

> "UBool" and "TRUE" are defined in "umachine.h", which is a header file for the
> "libicu" library.
>
> PostgreSQL includes "unicode/ucol.h", which will include "umachine.h"
> (via "utypes.h"), so that should be fine.
>
> Are your libicu headers installed under /usr/include/unicode?
> Do you get any messages about missing include files earlier?

It looks like something happened to ICU's boolean macros .  See this
commit in FreeBSD ports:

https://github.com/freebsd/freebsd-ports/commit/81a88b4506ec06d07be10d199170ef4003eb0e30

... which references:

https://github.com/unicode-org/icu/commit/c3fe7e09d844

Logical replication gradually slowing down, then hanging.

[Lukasz Biegaj]

Hello,

I'm encountering a repeating problem with logical replication.

The issue began occurring right after upgrading the cluster from 10.x to 
13.x.


There are two databases - `mc` and `comm` - within the same cluster. Few 
tables are replicated logically from `mc` to `comm`. The problem is that 
the replication gradually slows down (causing WAL storage to be 
extended), eventually leading to seemingly complete stop.


The WALSender process is caught in some kind of loop and I'm unable to 
either pg_cancel_backend or pg_terminate_backend it.
After some time, PostgreSQL notices that and tries to spawn another 
WALSender process, unfortunately the slot is already taken so this fails 
too.


The only way to restart the replication is to either restart the whole 
cluster or to force exit(1) on the walsender process by using gdb for 
example.


After such restart the replications starts at full speed. If there's a 
lot of data to process, then I may have to restart it more than once, as 
the problem with slowing down and stopping repeats.


At current flow the issue occurs every few hours. There are no log 
entries as to why this my occur. The replication is not locked by other 
queries/transactions.


I've captured the strace of walsender right before the 'hang': 
https://gist.github.com/lpiob/09088d9b0d9becebe3a213fe6f15b5ed


And also a gdb backtrace:
(gdb) bt
#0  0x5623348d3ce0 in hash_seq_search ()
#1  0x56233473a396 in ReorderBufferQueueChange ()
#2  0x56233472fb80 in LogicalDecodingProcessRecord ()
#3  0x5623347542e3 in ?? ()
#4  0x562334756992 in ?? ()
#5  0x5623347576ff in exec_replication_command ()
#6  0x56233479c9c5 in PostgresMain ()
#7  0x56233446d6f2 in ?? ()
#8  0x56233471ec5e in PostmasterMain ()
#9  0x56233446e91a in main ()
(gdb)


The issue I'm experiencing look awfully similar to following one:
https://www.postgresql.org/message-id/6fa054d8-ad14-42a2-8926-5d79c97ec...@matrix.gatewaynet.com

Although in my case, there are no schema changes.

I've tried dumping and restoring the database on separate host, setting 
up the replication from scratch. I've ruled out hardware issues or 
depleted disk resources. Raising the wal_receiver_timeout or 
wal_sender_timeout has no effect - it seems that the setting is 
completely ignored.


Please advise on how to debug the issue further or how to resolve it. 
I'm completely at loss as to the reasons why it may be happening.




--
Lukasz Biegaj | Unity Group | https://www.unitygroup.com/
System Architect, AWS Solutions Architect

Re: "invalid record length" after restoring pg_basebackup

[Dennis Jacobfeuerborn]

On 11/13/20 4:02 PM, Tom Lane wrote:
> Dennis Jacobfeuerborn  writes:
>> All of this works fine and the logs report that the db reaches a
>> consistent recovery state but as last entry it reports an "invalid
>> record length":
> 
> This looks quite normal to me.  If you'd pulled the power plug on the
> primary system at the time you made this backup, you would likely see
> the same message at the end of its crash recovery.  Some sort of
> corrupt-WAL-entry report is expected at the end of WAL replay anytime
> you didn't have a clean shutdown.

But the system the backup was pulled from kept running fine. Also
wouldn't that make re-attaching the system to the primary impossible
since replication cannot be continued due to the broken WAL record?
What I would expect is that pg_basebackup only transfer healthy WAL
entries so that a restored system can pick up right after that with
streaming replication.

Regards,
 Dennis

psycopg3 COPY support

[Daniele Varrazzo]

Hello,

I have written an article describing the new COPY support available in
psycopg3: it is a big improvement to what is available in psycopg2,
allowing COPY from a stream of Python objects, async operations,
binary copy. You can find it at
https://www.psycopg.org/articles/2020/11/15/psycopg3-copy/

In the next few days I would like to write more about the new main
features of psycopg3 and differences with psycopg2. In the meantime I
am writing down a first draft of the documentation
(https://www.psycopg.org/psycopg3/docs/)... and of course the code
that remains to write.

I am currently developing psycopg3 as my main activity: getting enough
funding for the project would put me in condition to develop it full
time and to release it quickly. If you or your company use Python and
PostgreSQL professionally and you would like to support the
development and maintenance of psycopg2 and psycopg3 your contribution
will be very appreciated.

More information about the psycopg3 project is at
https://www.psycopg.org/psycopg3/ Thank you very much!

-- Daniele

Re: Unable to compile postgres 13.1 on Slackware current x64

[Condor]

On 16-11-2020 11:10, Laurenz Albe wrote:

On Mon, 2020-11-16 at 09:15 +0200, Condor wrote:

unable to compile Postgresql 13.0 and 13.1 on Slackware current x64.
Here is gcc -v:

Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/9.3.0/specs
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-slackware-linux/9.3.0/lto-wrapper
Target: x86_64-slackware-linux
Configured with: ../configure --prefix=/usr --libdir=/usr/lib64
--mandir=/usr/man --infodir=/usr/info --enable-shared 
--enable-bootstrap

--enable-languages=ada,brig,c,c++,d,fortran,go,lto,objc,obj-c++
--enable-threads=posix --enable-checking=release --enable-objc-gc
--with-system-zlib --enable-libstdcxx-dual-abi
--with-default-libstdcxx-abi=new --disable-libstdcxx-pch
--disable-libunwind-exceptions --enable-__cxa_atexit --disable-libssp
--enable-gnu-unique-object --enable-plugin --enable-lto
--disable-install-libiberty --disable-werror --with-gnu-ld --with-isl
--verbose --with-arch-directory=amd64 --disable-gtktest
--enable-clocale=gnu --disable-multilib 
--target=x86_64-slackware-linux

--build=x86_64-slackware-linux --host=x86_64-slackware-linux
Thread model: posix
gcc version 9.3.0 (GCC)


ICU version - 68.1, LLVM version - 11.0.0


Here is configure params:
./configure \
   --prefix=/usr/lib$LIBDIRSUFFIX/postgresql/$VER \
   --libdir=/usr/lib$LIBDIRSUFFIX/postgresql/$VER/lib \
   --includedir=/usr/include \
   --sysconfdir=/etc/postgresql \
   --localstatedir=/var/lib/postgresql \
   --with-tcl \
   --with-tclconfig=/usr/lib$LIBDIRSUFFIX \
   --with-perl \
   --with-python \
   --with-openssl \
   --with-libxml \
   --with-libxslt \
   --with-icu \
   --with-llvm \
   --enable-thread-safety \
   --with-system-tzdata=/usr/share/zoneinfo \
   $ARCH-slackware-linux

The error is:

make[2]: Leaving directory '/tmp/postgresql-13.1/src/backend/utils'
make[1]: Leaving directory '/tmp/postgresql-13.1/src/backend'
x86_64-slackware-linux-gcc -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Werror=vla -Wendif-labels
-Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wformat-security
-fno-strict-aliasing -fwrapv -fexcess-precision=standard
-Wno-format-truncation -Wno-stringop-truncation -O2
-I../../../src/include  -D_GNU_SOURCE -I/usr/include/libxml2   -c -o
collationcmds.o collationcmds.c
collationcmds.c: In function ‘get_icu_language_tag’:
collationcmds.c:467:51: error: ‘TRUE’ undeclared (first use in this
function); did you mean ‘IS_TRUE’?
   467 |  uloc_toLanguageTag(localename, buf, sizeof(buf), TRUE, 
&status);

   |   ^~~~
   |   IS_TRUE

collationcmds.c:467:51: note: each undeclared identifier is reported
only once for each function it appears in
make: *** [: collationcmds.o] Error 1

Changing TRUE to IS_TRUE solve the problem and code is compiled but no
idea is this a real fix.


"UBool" and "TRUE" are defined in "umachine.h", which is a header file 
for the

"libicu" library.

PostgreSQL includes "unicode/ucol.h", which will include "umachine.h"
(via "utypes.h"), so that should be fine.

Are your libicu headers installed under /usr/include/unicode?
Do you get any messages about missing include files earlier?

Yours,
Laurenz Albe



Hello,

yes. My header files are installed in /usr/include/unicode and for the 
moment I don't get any messages

about missing files.

Best Regards,
HS

Re: "invalid record length" after restoring pg_basebackup

[Tom Lane]

Dennis Jacobfeuerborn  writes:
> On 11/13/20 4:02 PM, Tom Lane wrote:
>> This looks quite normal to me.  If you'd pulled the power plug on the
>> primary system at the time you made this backup, you would likely see
>> the same message at the end of its crash recovery.  Some sort of
>> corrupt-WAL-entry report is expected at the end of WAL replay anytime
>> you didn't have a clean shutdown.

> But the system the backup was pulled from kept running fine. Also
> wouldn't that make re-attaching the system to the primary impossible
> since replication cannot be continued due to the broken WAL record?

There is no "broken WAL record".  There is only junk following the
primary's current WAL write point.

> What I would expect is that pg_basebackup only transfer healthy WAL
> entries so that a restored system can pick up right after that with
> streaming replication.

You need to adjust your expectations.  pg_basebackup doesn't parse the WAL
data, because it has no need to.  It just copies whole WAL segment files.

regards, tom lane

Re: Unable to compile postgres 13.1 on Slackware current x64

[Laurenz Albe]

On Mon, 2020-11-16 at 22:17 +1300, Thomas Munro wrote:
> On Mon, Nov 16, 2020 at 10:10 PM Laurenz Albe  
> wrote:
> 
> > On Mon, 2020-11-16 at 09:15 +0200, Condor wrote:
> > > collationcmds.c: In function ‘get_icu_language_tag’:
> > > collationcmds.c:467:51: error: ‘TRUE’ undeclared (first use in this
> > > function); did you mean ‘IS_TRUE’?
> > > 467 |  uloc_toLanguageTag(localename, buf, sizeof(buf), TRUE, 
> > > &status);
> > > |   ^~~~
> > > |   IS_TRUE
> 
> 
> > "UBool" and "TRUE" are defined in "umachine.h", which is a header file for 
> > the
> > "libicu" library.
> > PostgreSQL includes "unicode/ucol.h", which will include "umachine.h"
> > (via "utypes.h"), so that should be fine.
> > Are your libicu headers installed under /usr/include/unicode?
> > Do you get any messages about missing include files earlier?
> 
> It looks like something happened to ICU's boolean macros .  See this
> commit in FreeBSD ports:
> 
> https://github.com/freebsd/freebsd-ports/commit/81a88b4506ec06d07be10d199170ef4003eb0e30
> 
> ... which references:
> 
> https://github.com/unicode-org/icu/commit/c3fe7e09d844

Ugh, you are right.  Joy.
This will be annoying to work around.

Yours,
Laurenz Albe

Re: Unable to compile postgres 13.1 on Slackware current x64

[Tom Lane]

Thomas Munro  writes:
> It looks like something happened to ICU's boolean macros .  See this
> commit in FreeBSD ports:

> https://github.com/freebsd/freebsd-ports/commit/81a88b4506ec06d07be10d199170ef4003eb0e30

It'd be so nice if people would tell us about their problems, instead of
just hacking-and-slashing.

In this case, I see one use of the constant TRUE in collationcmds.c,
but I wonder how come that's there given that we deprecated upper-case
TRUE some time ago.  I find it hard to believe that sprinkling "#include
" into random places is either necessary (on modern platforms
anyway) or a good idea (if we're not using , this seems pretty
much guaranteed to break things); so I think the rest of that patch is
foolhardy.

regards, tom lane

autovacuum recommendations for Large tables

[Atul Kumar]

Hi,

I have a large table having no. of live tuples approx 7690798868 and
no. of dead tuples approx 114917737.

So Please share autovacuum tuning recommendations for this table so
that our time can be spent better than repeatedly vacuuming large
tables.


Please help.



Regards,
Atul

Re: Unable to compile postgres 13.1 on Slackware current x64

[Laurenz Albe]

On Mon, 2020-11-16 at 12:30 -0500, Tom Lane wrote:
> Thomas Munro  writes:
> > It looks like something happened to ICU's boolean macros .  See this
> > commit in FreeBSD ports:
> > https://github.com/freebsd/freebsd-ports/commit/81a88b4506ec06d07be10d199170ef4003eb0e30
> 
> It'd be so nice if people would tell us about their problems, instead of
> just hacking-and-slashing.
> 
> In this case, I see one use of the constant TRUE in collationcmds.c,
> but I wonder how come that's there given that we deprecated upper-case
> TRUE some time ago.  I find it hard to believe that sprinkling "#include
> " into random places is either necessary (on modern platforms
> anyway) or a good idea (if we're not using , this seems pretty
> much guaranteed to break things); so I think the rest of that patch is
> foolhardy.

How about this patch?  It fixes the problem for me.

Yours,
Laurenz Albe
From 393a0a0c75cf74d93c6186ea00ff34f6b96df011 Mon Sep 17 00:00:00 2001
From: Laurenz Albe 
Date: Mon, 16 Nov 2020 19:01:22 +0100
Subject: [PATCH] Fix build for libicu 68 and later

ICU commit c3fe7e09d8 got rid of TRUE and FALSE and uses
"true" and "false" from "stdbool.h" instead.
Reported by Atul Kumar, diagnosis by Thomas Munro.
---
 src/include/utils/pg_locale.h | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/src/include/utils/pg_locale.h b/src/include/utils/pg_locale.h
index 96da132c03..cf20dbc049 100644
--- a/src/include/utils/pg_locale.h
+++ b/src/include/utils/pg_locale.h
@@ -34,6 +34,12 @@
 #endif
 #endif
 
+/* ICU 68 has got rid of TRUE and FALSE and uses stdbool.h instead */
+#if U_ICU_VERSION_MAJOR_NUM >= 68
+#define TRUE  true
+#define FALSE false
+#endif
+
 
 /* GUC settings */
 extern char *locale_messages;
-- 
2.26.2

Re: Unable to compile postgres 13.1 on Slackware current x64

[Tom Lane]

Laurenz Albe  writes:
> On Mon, 2020-11-16 at 12:30 -0500, Tom Lane wrote:
>> In this case, I see one use of the constant TRUE in collationcmds.c,
>> but I wonder how come that's there given that we deprecated upper-case
>> TRUE some time ago.  I find it hard to believe that sprinkling "#include
>> " into random places is either necessary (on modern platforms
>> anyway) or a good idea (if we're not using , this seems pretty
>> much guaranteed to break things); so I think the rest of that patch is
>> foolhardy.

> How about this patch?  It fixes the problem for me.

What's wrong with s/TRUE/true/ in get_icu_language_tag?
(I have zero interest in undoing 6337865f3, which is what this patch
would amount to.)

A larger issue is that it looks like ICU68 may insist on importing
 in some headers.  That's fine on the platforms where we
use  anyway, but it's distinctly not fine elsewhere.
We might be able to work around that the same way that dfmgr.h does:

/*
 * On macOS,  insists on including .  If we're not
 * using stdbool, undef bool to undo the damage.
 */
#ifndef PG_USE_STDBOOL
#ifdef bool
#undef bool
#endif
#endif

This is going to be hard to test without a platform that doesn't use
 though.  [ starts booting up spare PPC Mac ... ]

regards, tom lane

Re: Unable to compile postgres 13.1 on Slackware current x64

[Tom Lane]

I wrote:
> A larger issue is that it looks like ICU68 may insist on importing
>  in some headers.  That's fine on the platforms where we
> use  anyway, but it's distinctly not fine elsewhere.

Meh.  I went to see if I could test that, and didn't get much further
than this on ICU's downloads page:

ICU4C Platform Support

All: Compiler support for C++11 is required for building the ICU libraries.
Some platforms (such as IBM AIX, IBM z and Solaris) may no longer be able 
to build ICU until an improved compiler is available.

AFAIK, the only platforms we have where  isn't used are
PPC Mac, which of course was discontinued around 2008, so there's
zero chance that the compiler supports C++11.  Barring somebody
finding evidence of a platform that can run ICU68 and is not using
, it's not worth spending time on this combination.

I think we should just s/TRUE/true/ and be done with it.

regards, tom lane

Re: autovacuum recommendations for Large tables

[Andreas Schmitz]

https://www.postgresql.org/docs/13/routine-vacuuming.html

Regards

Andreas

Am 11/16/2020 um 6:38 PM schrieb Atul Kumar:
> Hi,
>
> I have a large table having no. of live tuples approx 7690798868 and
> no. of dead tuples approx 114917737.
>
> So Please share autovacuum tuning recommendations for this table so
> that our time can be spent better than repeatedly vacuuming large
> tables.
>
>
> Please help.
>
>
>
> Regards,
> Atul
>
>

Re: Unable to compile postgres 13.1 on Slackware current x64

[Tom Lane]

I wrote:
> What's wrong with s/TRUE/true/ in get_icu_language_tag?

I confirmed that that fixes the build with ICU 68.1, and pushed it.

regards, tom lane

Re: autovacuum recommendations for Large tables

[Atul Kumar]

Hi,

Could you help me by explaining in simple words, as I am new to postgres.

What value of which parameter should I set and why.

I only have this one big table in the database of size 3113 GB with rows
7661353111.

Right Now the autovacuum setting for that table is set to
{autovacuum_enabled=true,autovacuum_vacuum_scale_
factor=0.2,autovacuum_analyze_scale_factor=0.2}

Please help.






Regards
Atul






On Tuesday, November 17, 2020, Olivier Gautherot 
wrote:

> Hi Atul,
>
> I would start with a factor of 0.1 (10 parts per million) and explore
> down to 0.01.
>
> I did some massive updates on a partition with 12 millions rows and my
> factor was 0.001.
>
> Depending on the number of big tables you have in the database, you may
> wish to reduce the number of parallel workers.
>
> Hope it helps
> --
> Olivier Gautherot
> Tel: +33 6 02 71 92 23
> https://www.linkedin.com/in/ogautherot/
>
>
>
> 
>  Libre
> de virus. www.avast.com
> 
> <#m_-4472748644679516424_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Mon, Nov 16, 2020 at 8:20 PM Atul Kumar  wrote:
>
>> Ok,
>>
>> Right Now the autovacuum setting for that table is set to
>> {autovacuum_enabled=true,autovacuum_vacuum_scale_
>> factor=0.2,autovacuum_analyze_scale_factor=0.2}
>>
>>
>> So Please suggest, how much should i set atleast, to avoid increasing
>> in dead tuple.
>>
>>
>>
>> Regards,
>> Atul
>>
>>
>>
>> On 11/16/20, Olivier Gautherot  wrote:
>> > Hi Atul,
>> >
>> > Le lun. 16 nov. 2020 à 18:38, Atul Kumar  a
>> écrit :
>> >
>> >> Hi,
>> >>
>> >> I have a large table having no. of live tuples approx 7690798868 and
>> >> no. of dead tuples approx 114917737.
>> >>
>> >> So Please share autovacuum tuning recommendations for this table so
>> >> that our time can be spent better than repeatedly vacuuming large
>> >> tables.
>> >>
>> >
>> > Vacuuming will affect you when it has a lot of work to do. I would try
>> to
>> > trigger an autovacuum every 10,000 insert/update to minimize the impact.
>> > You can play with the parameter autovacuum_vacuum_scale_factor for that
>> > table.
>> >
>> > Good luck
>> > Olivier
>> >
>>
>

Re: autovacuum recommendations for Large tables

[David G. Johnston]

On Mon, Nov 16, 2020 at 3:57 PM Atul Kumar  wrote:

> I only have this one big table in the database of size 3113 GB with rows
> 7661353111.
>
> Right Now the autovacuum setting for that table is set to
>
> {autovacuum_enabled=true,autovacuum_vacuum_scale_factor=0.2,autovacuum_analyze_scale_factor=0.2}
>
>>
>>>
auto-vacuum doesn't care directly about absolute size, it cares about
change (relative to absolute size in many cases, hence the scale factors).

David J.

RE: New "function tables" in V13 documentation

[Kevin Brannen]

>From: Adrian Klaver 
>>On 11/15/20 9:00 AM, David G. Johnston wrote:
>
>> In hindsight it could have been handled better.  Waiting longer at
>> different points and making pronouncements on -announce to solicit
>> feedback from people who don't follow -docs.  That doesn't change the

> Yes and at least one post to --general. It would have motivated me to look at 
> the new docs earlier.

+1 on the post to -general.

FWIW... My attention to -announce is lazy but I'd see that eventually. I get a 
little behind on -general from time to time, but this is where I pay the most 
attention. I have no idea where most people are, perhaps the list maintainers 
could give some guidance on that.

HTH,
Kevin
This e-mail transmission, and any documents, files or previous e-mail messages 
attached to it, may contain confidential information. If you are not the 
intended recipient, or a person responsible for delivering it to the intended 
recipient, you are hereby notified that any disclosure, distribution, review, 
copy or use of any of the information contained in or attached to this message 
is STRICTLY PROHIBITED. If you have received this transmission in error, please 
immediately notify us by reply e-mail, and destroy the original transmission 
and its attachments without reading them or saving them to disk. Thank you.

Re: I have just downloaded Postgre SQL and "pgadmin 4" doesn't open.

[Ecenur Corlu]

Hello Mr. Klaver,
 I couldn't solve the problem on my computer. I also download it from

https://www.enterprisedb.com/downloads/postgres-postgresql-downloads but
nothing has changed.
I looked at system logs but I couldn't  find the relevant error log.

So, I downloaded PostgreSQL on somebody else's computer.
Thank you, for your help. I really appreciate it.
Ece


Adrian Klaver , 15 Kas 2020 Paz, 19:49 tarihinde
şunu yazdı:

> On 11/15/20 4:51 AM, Ecenur Corlu wrote:
> > Hello Mr Klaver,
> >
> > I downloaded it from
> > "https://www.enterprisedb.com/software-downloads-postgres
> > "
>
> The above needs an account to access. Is this one of the EDB paid
> versions of Postgres?
>
> The community edition(if that is what yiu want) can be found here:
>
> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
>
> > I start it by just clicking on "pgadmin 4" from the start menu. I also
> > tried starting it by clicking on "run as administrator"
>
>
> Have you looked at the Windows system logs to see if there are any
> relevant errors?
>
> FYI, per your looking for the pgAdmin binaries they will be found here:
>
> C:\Program Files\PostgreSQL\13\pgAdmin4
>
> >
> > My system is :
> > Windows 10
> > Ram 12GB (11.9 GB usable Ram)
> > Intel(R) Core (TM) i7-4700HQ CPU @ 2.40GHz
> > x64
> >
> > Thank you for your reply.
> > Ece
> >
> >
> >
> > Adrian Klaver  > >, 15 Kas 2020 Paz, 03:08 tarihinde
> > şunu yazdı:
> >
> > On 11/14/20 3:45 PM, Ecenur Corlu wrote:
> >  > *I have just downloaded the latest version of PostgreSQL
> > (vs.13.1) and
> >
> > Where did you download it from?
> >
> > More comments inline below.
> >
> >  > when I try to open "pgadmin 4", it doesn't open.* It first shows
> >
> > How are you starting it?
> >
> >  > */windows wait cursor/* and then the wait cursor gets lost.
> > Nothing happens.
> >  >
> >  > *I also realized that there is no folder created under* C:\Program
> >  > Files. *like this* >>>"C:\Program Files\pgAdmin 4" I can't find
> > log docs.
> >  >
> >  > I have also tried these methods.
> >  >
> >  >  1. I have deleted PostgreSQL and re-downloaded it. It didn't
> > make any
> >  > difference. The same mistake is happening again.
> >  >  2. I have downloaded Java.
> >
> > pgAdmin uses Python/JS/CSS/HTML. Java is not a requirement.
> >
> >  >  3. I have looked at "HKEY_CLASSES_ROOT.css\Content Type" to see
> if
> >  > "text/css" is written there. And it was in "text/css" format,
> so
> >  > there wasn't any mistake there.
> >  >  4. I deleted "Anaconda" which was downloaded on my computer. I
> have
> >  > read that it blocks pgadmin 4 to start.
> >  >  5. I made Chrome my default browser.
> >  >  6. I added in "HKEY_CLASSES_ROOT.jz" a value name: "Content
> Type" in
> >  > "Reg SZ" type and it's data is "text/javascript" .Previously
> > there
> >  > was just"default" value name and it's data was "JSFile"
> Ihaven't
> >  > deleted this yet.
> >  >
> >  >
> >  > Thank you in advance for your help.
> >  >
> >
> >
> > --
> > Adrian Klaver
> > adrian.kla...@aklaver.com 
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: I have just downloaded Postgre SQL and "pgadmin 4" doesn't open.

[Adrian Klaver]

On 11/16/20 8:59 PM, Ecenur Corlu wrote:

Hello Mr. Klaver,
  I couldn't solve the problem on my computer. I also download it from

https://www.enterprisedb.com/downloads/postgres-postgresql-downloads 
 but 
nothing has changed.

I looked at system logs but I couldn't  find the relevant error log.

So, I downloaded PostgreSQL on somebody else's computer.


So did it work there?
If so what was OS and version on that computer?


Thank you, for your help. I really appreciate it.
Ece


Adrian Klaver >, 15 Kas 2020 Paz, 19:49 tarihinde 
şunu yazdı:


On 11/15/20 4:51 AM, Ecenur Corlu wrote:
 > Hello Mr Klaver,
 >
 > I downloaded it from
 > "https://www.enterprisedb.com/software-downloads-postgres

 > >"

The above needs an account to access. Is this one of the EDB paid
versions of Postgres?

The community edition(if that is what yiu want) can be found here:

https://www.enterprisedb.com/downloads/postgres-postgresql-downloads


 > I start it by just clicking on "pgadmin 4" from the start menu. I
also
 > tried starting it by clicking on "run as administrator"


Have you looked at the Windows system logs to see if there are any
relevant errors?

FYI, per your looking for the pgAdmin binaries they will be found here:

C:\Program Files\PostgreSQL\13\pgAdmin4

 >
 > My system is :
 > Windows 10
 > Ram 12GB (11.9 GB usable Ram)
 > Intel(R) Core (TM) i7-4700HQ CPU @ 2.40GHz
 > x64
 >
 > Thank you for your reply.
 > Ece
 >
 >
 >
 > Adrian Klaver mailto:adrian.kla...@aklaver.com>
 > >>, 15 Kas 2020 Paz, 03:08 tarihinde
 > şunu yazdı:
 >
 >     On 11/14/20 3:45 PM, Ecenur Corlu wrote:
 >      > *I have just downloaded the latest version of PostgreSQL
 >     (vs.13.1) and
 >
 >     Where did you download it from?
 >
 >     More comments inline below.
 >
 >      > when I try to open "pgadmin 4", it doesn't open.* It first
shows
 >
 >     How are you starting it?
 >
 >      > */windows wait cursor/* and then the wait cursor gets lost.
 >     Nothing happens.
 >      >
 >      > *I also realized that there is no folder created
under* C:\Program
 >      > Files. *like this* >>>"C:\Program Files\pgAdmin 4" I can't
find
 >     log docs.
 >      >
 >      > I have also tried these methods.
 >      >
 >      >  1. I have deleted PostgreSQL and re-downloaded it. It didn't
 >     make any
 >      >     difference. The same mistake is happening again.
 >      >  2. I have downloaded Java.
 >
 >     pgAdmin uses Python/JS/CSS/HTML. Java is not a requirement.
 >
 >      >  3. I have looked at "HKEY_CLASSES_ROOT.css\Content Type"
to see if
 >      >     "text/css" is written there. And it was in "text/css"
format, so
 >      >     there wasn't any mistake there.
 >      >  4. I deleted "Anaconda" which was downloaded on my
computer. I have
 >      >     read that it blocks pgadmin 4 to start.
 >      >  5. I made Chrome my default browser.
 >      >  6. I added in "HKEY_CLASSES_ROOT.jz" a value name:
"Content Type" in
 >      >     "Reg SZ" type and it's data is "text/javascript"
.Previously
 >     there
 >      >     was just"default" value name and it's data was
"JSFile" Ihaven't
 >      >     deleted this yet.
 >      >
 >      >
 >      > Thank you in advance for your help.
 >      >
 >
 >
 >     --
 >     Adrian Klaver
 > adrian.kla...@aklaver.com 
>
 >


-- 
Adrian Klaver

adrian.kla...@aklaver.com 




--
Adrian Klaver
adrian.kla...@aklaver.com

Re: I have just downloaded Postgre SQL and "pgadmin 4" doesn't open.

[Ecenur Corlu]

Yes it worked.
Intel (R) Core (TM) İ7-6700HQ CPU @2.60 Ghz 2.59 GHz - 16.0GB Ram- x64
I downloaded 13.1 Version from here.
"https://www.enterprisedb.com/software-downloads-postgres
I'll work there. Thank you.
Ece

Adrian Klaver , 17 Kas 2020 Sal, 08:13 tarihinde
şunu yazdı:

> On 11/16/20 8:59 PM, Ecenur Corlu wrote:
> > Hello Mr. Klaver,
> >   I couldn't solve the problem on my computer. I also download it from
> >
> > https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
> >  but
>
> > nothing has changed.
> > I looked at system logs but I couldn't  find the relevant error log.
> >
> > So, I downloaded PostgreSQL on somebody else's computer.
>
> So did it work there?
> If so what was OS and version on that computer?
>
> > Thank you, for your help. I really appreciate it.
> > Ece
> >
> >
> > Adrian Klaver  > >, 15 Kas 2020 Paz, 19:49 tarihinde
> > şunu yazdı:
> >
> > On 11/15/20 4:51 AM, Ecenur Corlu wrote:
> >  > Hello Mr Klaver,
> >  >
> >  > I downloaded it from
> >  > "https://www.enterprisedb.com/software-downloads-postgres
> > 
> >  >  > >"
> >
> > The above needs an account to access. Is this one of the EDB paid
> > versions of Postgres?
> >
> > The community edition(if that is what yiu want) can be found here:
> >
> > https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
> > <
> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads>
> >
> >  > I start it by just clicking on "pgadmin 4" from the start menu. I
> > also
> >  > tried starting it by clicking on "run as administrator"
> >
> >
> > Have you looked at the Windows system logs to see if there are any
> > relevant errors?
> >
> > FYI, per your looking for the pgAdmin binaries they will be found
> here:
> >
> > C:\Program Files\PostgreSQL\13\pgAdmin4
> >
> >  >
> >  > My system is :
> >  > Windows 10
> >  > Ram 12GB (11.9 GB usable Ram)
> >  > Intel(R) Core (TM) i7-4700HQ CPU @ 2.40GHz
> >  > x64
> >  >
> >  > Thank you for your reply.
> >  > Ece
> >  >
> >  >
> >  >
> >  > Adrian Klaver  > 
> >  >  > >>, 15 Kas 2020 Paz, 03:08
> tarihinde
> >  > şunu yazdı:
> >  >
> >  > On 11/14/20 3:45 PM, Ecenur Corlu wrote:
> >  >  > *I have just downloaded the latest version of PostgreSQL
> >  > (vs.13.1) and
> >  >
> >  > Where did you download it from?
> >  >
> >  > More comments inline below.
> >  >
> >  >  > when I try to open "pgadmin 4", it doesn't open.* It first
> > shows
> >  >
> >  > How are you starting it?
> >  >
> >  >  > */windows wait cursor/* and then the wait cursor gets lost.
> >  > Nothing happens.
> >  >  >
> >  >  > *I also realized that there is no folder created
> > under* C:\Program
> >  >  > Files. *like this* >>>"C:\Program Files\pgAdmin 4" I can't
> > find
> >  > log docs.
> >  >  >
> >  >  > I have also tried these methods.
> >  >  >
> >  >  >  1. I have deleted PostgreSQL and re-downloaded it. It
> didn't
> >  > make any
> >  >  > difference. The same mistake is happening again.
> >  >  >  2. I have downloaded Java.
> >  >
> >  > pgAdmin uses Python/JS/CSS/HTML. Java is not a requirement.
> >  >
> >  >  >  3. I have looked at "HKEY_CLASSES_ROOT.css\Content Type"
> > to see if
> >  >  > "text/css" is written there. And it was in "text/css"
> > format, so
> >  >  > there wasn't any mistake there.
> >  >  >  4. I deleted "Anaconda" which was downloaded on my
> > computer. I have
> >  >  > read that it blocks pgadmin 4 to start.
> >  >  >  5. I made Chrome my default browser.
> >  >  >  6. I added in "HKEY_CLASSES_ROOT.jz" a value name:
> > "Content Type" in
> >  >  > "Reg SZ" type and it's data is "text/javascript"
> > .Previously
> >  > there
> >  >  > was just"default" value name and it's data was
> > "JSFile" Ihaven't
> >  >  > deleted this yet.
> >  >  >
> >  >  >
> >  >  > Thank you in advance for your help.
> >  >  >
> >  >
> >  >
> >  > --
> >  > Adrian Klaver
> >  > adrian.kla...@aklaver.com 
> >  >>
> >  >
> >
> >
> > --
> > Adrian Kla

Re: I have just downloaded Postgre SQL and "pgadmin 4" doesn't open.

[Ecenur Corlu]

  It is Windows 10  too.

Ecenur Corlu , 17 Kas 2020 Sal, 08:26 tarihinde şunu
yazdı:

> Yes it worked.
> Intel (R) Core (TM) İ7-6700HQ CPU @2.60 Ghz 2.59 GHz - 16.0GB Ram- x64
> I downloaded 13.1 Version from here.
> "https://www.enterprisedb.com/software-downloads-postgres
> I'll work there. Thank you.
> Ece
>
> Adrian Klaver , 17 Kas 2020 Sal, 08:13
> tarihinde şunu yazdı:
>
>> On 11/16/20 8:59 PM, Ecenur Corlu wrote:
>> > Hello Mr. Klaver,
>> >   I couldn't solve the problem on my computer. I also download it from
>> >
>> > https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
>> >  but
>>
>> > nothing has changed.
>> > I looked at system logs but I couldn't  find the relevant error log.
>> >
>> > So, I downloaded PostgreSQL on somebody else's computer.
>>
>> So did it work there?
>> If so what was OS and version on that computer?
>>
>> > Thank you, for your help. I really appreciate it.
>> > Ece
>> >
>> >
>> > Adrian Klaver > > >, 15 Kas 2020 Paz, 19:49 tarihinde
>> > şunu yazdı:
>> >
>> > On 11/15/20 4:51 AM, Ecenur Corlu wrote:
>> >  > Hello Mr Klaver,
>> >  >
>> >  > I downloaded it from
>> >  > "https://www.enterprisedb.com/software-downloads-postgres
>> > 
>> >  > > > >"
>> >
>> > The above needs an account to access. Is this one of the EDB paid
>> > versions of Postgres?
>> >
>> > The community edition(if that is what yiu want) can be found here:
>> >
>> >
>> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
>> > <
>> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads>
>> >
>> >  > I start it by just clicking on "pgadmin 4" from the start menu. I
>> > also
>> >  > tried starting it by clicking on "run as administrator"
>> >
>> >
>> > Have you looked at the Windows system logs to see if there are any
>> > relevant errors?
>> >
>> > FYI, per your looking for the pgAdmin binaries they will be found
>> here:
>> >
>> > C:\Program Files\PostgreSQL\13\pgAdmin4
>> >
>> >  >
>> >  > My system is :
>> >  > Windows 10
>> >  > Ram 12GB (11.9 GB usable Ram)
>> >  > Intel(R) Core (TM) i7-4700HQ CPU @ 2.40GHz
>> >  > x64
>> >  >
>> >  > Thank you for your reply.
>> >  > Ece
>> >  >
>> >  >
>> >  >
>> >  > Adrian Klaver > > 
>> >  > > > >>, 15 Kas 2020 Paz, 03:08
>> tarihinde
>> >  > şunu yazdı:
>> >  >
>> >  > On 11/14/20 3:45 PM, Ecenur Corlu wrote:
>> >  >  > *I have just downloaded the latest version of PostgreSQL
>> >  > (vs.13.1) and
>> >  >
>> >  > Where did you download it from?
>> >  >
>> >  > More comments inline below.
>> >  >
>> >  >  > when I try to open "pgadmin 4", it doesn't open.* It first
>> > shows
>> >  >
>> >  > How are you starting it?
>> >  >
>> >  >  > */windows wait cursor/* and then the wait cursor gets
>> lost.
>> >  > Nothing happens.
>> >  >  >
>> >  >  > *I also realized that there is no folder created
>> > under* C:\Program
>> >  >  > Files. *like this* >>>"C:\Program Files\pgAdmin 4" I can't
>> > find
>> >  > log docs.
>> >  >  >
>> >  >  > I have also tried these methods.
>> >  >  >
>> >  >  >  1. I have deleted PostgreSQL and re-downloaded it. It
>> didn't
>> >  > make any
>> >  >  > difference. The same mistake is happening again.
>> >  >  >  2. I have downloaded Java.
>> >  >
>> >  > pgAdmin uses Python/JS/CSS/HTML. Java is not a requirement.
>> >  >
>> >  >  >  3. I have looked at "HKEY_CLASSES_ROOT.css\Content Type"
>> > to see if
>> >  >  > "text/css" is written there. And it was in "text/css"
>> > format, so
>> >  >  > there wasn't any mistake there.
>> >  >  >  4. I deleted "Anaconda" which was downloaded on my
>> > computer. I have
>> >  >  > read that it blocks pgadmin 4 to start.
>> >  >  >  5. I made Chrome my default browser.
>> >  >  >  6. I added in "HKEY_CLASSES_ROOT.jz" a value name:
>> > "Content Type" in
>> >  >  > "Reg SZ" type and it's data is "text/javascript"
>> > .Previously
>> >  > there
>> >  >  > was just"default" value name and it's data was
>> > "JSFile" Ihaven't
>> >  >  > deleted this yet.
>> >  >  >
>> >  >  >
>> >  >  > Thank you in advance for your help.
>> >  >  >
>> >  >
>> >  >
>> >  >  

Re: Unable to compile postgres 13.1 on Slackware current x64

[Condor]

On 16-11-2020 22:18, Tom Lane wrote:

I wrote:

What's wrong with s/TRUE/true/ in get_icu_language_tag?


I confirmed that that fixes the build with ICU 68.1, and pushed it.

regards, tom lane



Hello,

I try to compile postgres again with (cd src/backend/commands; sed 
's/TRUE/true/' collationcmds.c > collationcmds.c; ) and it's compiled 
but get new error on linking:



src/backend/utils/fmgrtab.o ) >objfiles.txt
gmake[3]: Leaving directory '/tmp/postgresql-13.1/src/backend/utils'
x86_64-slackware-linux-gcc -Wall -Wmissing-prototypes -Wpointer-arith 
-Wdeclaration-after-statement -Werror=vla -Wendif-labels 
-Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard 
-Wno-format-truncation -Wno-stringop-truncation -O2 access/brin/brin.o 
access/brin/brin_inclusion.o access/brin/brin_minmax.o 
access/brin/brin_pageops.o access/brin/brin_revmap.o 
access/brin/brin_tuple.o access/brin/brin_validate.o 
access/brin/brin_xlog.o access/common/attmap.o access/common/bufmask.o 
access/common/detoast.o access/common/heaptuple.o 
access/common/indextuple.o access/common/printsimple.o 
access/common/printtup.o access/common/relation.o 
access/common/reloptions.o access/common/scankey.o 
access/common/session.o access/common/toast_internals.o 
access/common/tupconvert.o access/common/tupdesc.o 
access/gin/ginarrayproc.o access/gin/ginbtree.o access/gin/ginbulk.o 
access/gin/gindatapage.o access/gin/ginentrypage.o access/gin/ginfast.o 
access/gin/ginget.o access/gin/gininsert.o access/gin/ginlogic.o 
access/gin/ginpostinglist.o access/gin/ginscan.o access/gin/ginutil.o 
access/gin/ginvacuum.o access/gin/ginvalidate.o access/gin/ginxlog.o 
access/gist/gist.o access/gist/gistbuild.o 
access/gist/gistbuildbuffers.o access/gist/gistget.o 
access/gist/gistproc.o access/gist/gistscan.o access/gist/gistsplit.o 
access/gist/gistutil.o access/gist/gistvacuum.o 
access/gist/gistvalidate.o access/gist/gistxlog.o access/hash/hash.o 
access/hash/hash_xlog.o access/hash/hashfunc.o access/hash/hashinsert.o 
access/hash/hashovfl.o access/hash/hashpage.o access/hash/hashsearch.o 
access/hash/hashsort.o access/hash/hashutil.o access/hash/hashvalidate.o 
access/heap/heapam.o access/heap/heapam_handler.o 
access/heap/heapam_visibility.o access/heap/heaptoast.o 
access/heap/hio.o access/heap/pruneheap.o access/heap/rewriteheap.o 
access/heap/syncscan.o access/heap/vacuumlazy.o 
access/heap/visibilitymap.o access/index/amapi.o 
access/index/amvalidate.o access/index/genam.o access/index/indexam.o 
access/nbtree/nbtcompare.o access/nbtree/nbtdedup.o 
access/nbtree/nbtinsert.o access/nbtree/nbtpage.o access/nbtree/nbtree.o 
access/nbtree/nbtsearch.o access/nbtree/nbtsort.o 
access/nbtree/nbtsplitloc.o access/nbtree/nbtutils.o 
access/nbtree/nbtvalidate.o access/nbtree/nbtxlog.o 
access/rmgrdesc/brindesc.o access/rmgrdesc/clogdesc.o 
access/rmgrdesc/committsdesc.o access/rmgrdesc/dbasedesc.o 
access/rmgrdesc/genericdesc.o access/rmgrdesc/gindesc.o 
access/rmgrdesc/gistdesc.o access/rmgrdesc/hashdesc.o 
access/rmgrdesc/heapdesc.o access/rmgrdesc/logicalmsgdesc.o 
access/rmgrdesc/mxactdesc.o access/rmgrdesc/nbtdesc.o 
access/rmgrdesc/relmapdesc.o access/rmgrdesc/replorigindesc.o 
access/rmgrdesc/seqdesc.o access/rmgrdesc/smgrdesc.o 
access/rmgrdesc/spgdesc.o access/rmgrdesc/standbydesc.o 
access/rmgrdesc/tblspcdesc.o access/rmgrdesc/xactdesc.o 
access/rmgrdesc/xlogdesc.o access/spgist/spgdoinsert.o 
access/spgist/spginsert.o access/spgist/spgkdtreeproc.o 
access/spgist/spgproc.o access/spgist/spgquadtreeproc.o 
access/spgist/spgscan.o access/spgist/spgtextproc.o 
access/spgist/spgutils.o access/spgist/spgvacuum.o 
access/spgist/spgvalidate.o access/spgist/spgxlog.o access/table/table.o 
access/table/tableam.o access/table/tableamapi.o 
access/table/toast_helper.o access/tablesample/bernoulli.o 
access/tablesample/system.o access/tablesample/tablesample.o 
access/transam/clog.o access/transam/commit_ts.o 
access/transam/generic_xlog.o access/transam/multixact.o 
access/transam/parallel.o access/transam/rmgr.o access/transam/slru.o 
access/transam/subtrans.o access/transam/timeline.o 
access/transam/transam.o access/transam/twophase.o 
access/transam/twophase_rmgr.o access/transam/varsup.o 
access/transam/xact.o access/transam/xlog.o access/transam/xlogarchive.o 
access/transam/xlogfuncs.o access/transam/xloginsert.o 
access/transam/xlogreader.o access/transam/xlogutils.o 
bootstrap/bootparse.o bootstrap/bootstrap.o catalog/aclchk.o 
catalog/catalog.o catalog/dependency.o catalog/heap.o catalog/index.o 
catalog/indexing.o catalog/namespace.o catalog/objectaccess.o 
catalog/objectaddress.o catalog/partition.o catalog/pg_aggregate.o 
catalog/pg_cast.o catalog/pg_collation.o catalog/pg_constraint.o 
catalog/pg_conversion.o catalog/pg_db_role_setting.o catalog/pg_depend.o 
catalog/pg_enum.o catalog/pg_inherits.o catalog/pg_largeobject.o 
catalog/pg_namespace