On a 128MB RAM, 450 MHz pentium 3 server with linux gentoo and postgresql
7.4.6 on an office lan we can manage satisfactorily a db containing few
tables with a cumbersome amount of data (each table is around 650 thousand
records with 98 columns) relating to the year 2002.
We use M$-Access and ODBC
Dear all,
Context: FreeBSD postgresql 7.4.5, on a pentium 3 server 128MB.
I have a huge table letture02 made of 1,340,000 "freezed" records of 98
columns each (they do not change over time because the data are related
to measurements made in 2002 and 2003 there is no need to update them or,
worst
At office we have a Win2k LAN to which my freebsd postgresql server box
is connected via Samba. On this box I have a script, called 'crono', which
is dealt by /usr/bin/cron every working day's night at 1 am. As you can
see below this crono script vacuums all the DBs and dumps mydb to a samba
shar
DISMISS MY MESSAGE
Of course, it was a "slip of the tangue"!
Sorry to bother this esteemed ng.
Vittorio
:-- Messaggio originale --
:Date: Thu, 20 Jan 2005 15:10:45 +0100
:From: [EMAIL PROTECTED]
:To: "FreeBSD" ,
: "postgresql"
:Subject: Samba not showing public share et al.
:
:
:Server B
Server Box ():
Pentium 3
FreeBSD 5.3
Samba 3.0.7
connection to a windows 2000 LAN
Samba on the freebsd side has the following smb.conf:
[global]
workgroup = MYCO
#
server string = VicBSD
load printers = no
log file = /va
Context:Postgresql 7.4.6 under linux gentoo
To move a postgres DB from a FreeBSD box to al linux box I pg_dumped the
archive from the FreeBSD box and pg_restored into the linux box: Now when
I pg_dump the archive I get the following warnings for every table in the
archive:
...