Re: psql -f backup.out || file too big - SOLVED

From: Helge Bahmann <bahmann(at)math(dot)tu-freiberg(dot)de>
To: Jorge Sarmiento <jsarmiento(at)ccom(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: psql -f backup.out || file too big - SOLVED
Date: 2001-11-12 17:26:31
Message-ID: Pine.LNX.4.21.0111121819010.11635-100000@lothlorien.stunet2.tu-freiberg.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-announce pgsql-general pgsql-hackers

On Mon, 12 Nov 2001, Jorge Sarmiento wrote:

[backup.out > 2GB]
> the solution was:
>
> psql < backup.out
>
> instead of
>
> psql -f backup.out
[...]
> what that psql -f limit documented somewhere?

This is not a limitation of psql, but of lacking "large file support"
selected at compile time.

If you recompile psql and add the option "-D_FILE_OFFSET_BITS=64" then
psql -f should work as well.

Regards
--
Helge Bahmann <bahmann(at)math(dot)tu-freiberg(dot)de> /| \__
Network admin, systems programmer /_|____\
_/\ | __)
$ ./configure \\ \|__/__|
checking whether build environment is sane... yes \\/___/ |
checking for AIX... no (we already did this) |

In response to

Browse pgsql-announce by date

  From Date Subject
Next Message Marko Kreen 2001-11-25 19:22:09 pgcrypto 0.4
Previous Message Jorge Sarmiento 2001-11-12 16:09:01 Re: psql -f backup.out || file too big - SOLVED

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-11-12 17:33:42 Re: Creating languages with relative path to shared libraries
Previous Message Oberpriller, Wade D. 2001-11-12 16:10:49 Creating languages with relative path to shared libraries

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-11-12 17:36:49 Re: ALTER TABLE ADD COLUMN can't use NOT NULL?
Previous Message Bruce Momjian 2001-11-12 16:36:54 Re: Open items