Re: PostgreSQL for VAX on NetBSD/OpenBSD - Mailing list pgsql-hackers

Hi,

> What value did it select for shared_buffers?  How much memory does a
> high-end VAX have?  These days, we try to set shared_buffers = 128MB
> if the platform will support it, but it's supposed to fall back to
> smaller values if that doesn't work.  It will try allocating that much
> though, at least for a moment, to see whether it can.

A high end VAX, such as a 4000 Model 108, can have 512 megs (as can an 
11/780, at least in theory), but most of the VAXen used here are 
VAXstations such as the 4000/60 or 4000/90, 90a or 96, which have either 
104 megs or 128 megs.

I was trying it just using the default postgresql.conf. I changed it:

< max_connections = 10                  # (change requires restart)
> max_connections = 40                  # (change requires restart)
< shared_buffers = 16MB                 # min 128kB
> shared_buffers = 128MB                        # min 128kB
< temp_buffers = 2MB                    # min 800kB
< max_prepared_transactions = 0         # zero disables the feature
> #temp_buffers = 8MB                   # min 800kB
> #max_prepared_transactions = 0                # zero disables the feature
< maintenance_work_mem = 8MB            # min 1MB
< max_stack_depth = 1MB                 # min 100kB
> #maintenance_work_mem = 16MB          # min 1MB
> #max_stack_depth = 2MB                        # min 100kB
< max_files_per_process = 100           # min 25
> #max_files_per_process = 1000         # min 25


and it launched fine. I then tried to run:

gmake MAX_CONNECTIONS=5 installcheck

in /usr/pkgsrc/databases/postgresql93-server/work/postgresql-9.3.4/src/test/regress,
but it failed with:

...
gmake[2]: Leaving directory 
'/usr/pkgsrc/databases/postgresql93-server/work/postgresql-9.3.4/src/backend'
gcc -O1 -fgcse -fstrength-reduce -fgcse-after-reload -I/usr/include 
-I/usr/local/include -Wall -Wmissing-prototypes -Wpointer-arith 
-Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute 
-Wformat-security -fno-strict-aliasing -fwrapv -pthread  -mt -D_REENTRANT 
-D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -I../../src/port -DFRONTEND 
-I../../src/include -I/usr/include -I/usr/local/include   -c -o thread.o 
thread.c
cc1: error: unrecognized 
command line option "-mt" <builtin>: recipe for target 'thread.o' failed
gmake[1]: *** [thread.o] Error 1
gmake[1]: Leaving directory 
'/usr/pkgsrc/databases/postgresql93-server/work/postgresql-9.3.4/src/port'
../../../src/Makefile.global:423: recipe for target 'submake-libpgport' 
failed
gmake: *** [submake-libpgport] Error 2

That's all I have time for tonight. Is there an easier way to run a 
testsuite?

Thanks,
John