Skip site navigation (1) Skip section navigation (2)

Patch for allowing multiple -t <table-name> options for pg_dump

From: Andreas Joseph Krogh <andreak(at)officenet(dot)no>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Patch for allowing multiple -t <table-name> options for pg_dump
Date: 2003-10-01 14:00:08
Message-ID: 200310011600.24242.andreak@officenet.no (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This si my first look at the pg-code, so it may not comply with the 
coding-standards. I haven't coded in C for a while either, so if someone 
finds a better way to implement this, go ahead, but this patch works for me 
with 7.4beta3.

http://home.officenet.no/~andreak/pg_dump.c.diff

comments are welcome.

If it's ok, I'll remove my debuging statements and provide a cleaner patch.

- -- 
Andreas Joseph Krogh <andreak(at)officenet(dot)no>
Managing Director, Senior Software Developer
OfficeNet AS

- - Writing software is more fun than working.

gpg public_key: http://dev.officenet.no/~andreak/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/et34UopImDh2gfQRAqtBAKCcrJ3mlN5G6Jp3h3kz2G8zMlc2xgCeLmOv
844vwdmhcU4/VLjugW+ISF8=
=/hYF
-----END PGP SIGNATURE-----

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-10-01 14:31:22
Subject: Re: NOTICE: CREATE TABLE will create implicit triggers for foreign-key checks
Previous:From: Adam H. PendletonDate: 2003-10-01 13:53:24
Subject: Re: GPL code issue?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group