Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I just tried with current CVS and got:
> > $ aspg pg_dump --someoptionthatdoesntexist somedb
> > pg_dump: unrecognized option `--someoptionthatdoesntexist'
> > Try 'pg_dump --help' for more information.
> > My guess is th
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I just tried with current CVS and got:
> $ aspg pg_dump --someoptionthatdoesntexist somedb
> pg_dump: unrecognized option `--someoptionthatdoesntexist'
> Try 'pg_dump --help' for more information.
> My guess is that there is something
I just tried with current CVS and got:
$ aspg pg_dump --someoptionthatdoesntexist somedb
pg_dump: unrecognized option `--someoptionthatdoesntexist'
Try 'pg_dump --help' for more information.
My guess is that there is something buggy with your libc getopt. Can
Menno Smits ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
pg_dump segfaults when given an invalid command line option
Long Description
pg_dump crashes with a segmentation fault and dumps core when given an invalid command
li
Short Description
Inconsistency in the way that psql handles long names
Long Description
PostgreSQL version 7.1.3
OS: RedHat Linux 6.2
I compiled this version of postgresql from source, with the NAMEDATALEN
variable set to 512. All works ok, apart from when I use
the psql interactive terminal
On 18 Jul 2002, [ISO-8859-1] Stéphane Raimbault wrote:
> Hi,
>
> I have the following tables :
> CREATE TABLE tournee (
>no_tournee SERIAL PRIMARY KEY);
>
> CREATE TABLE fab_tournee (
>id SERIAL PRIMARY KEY,
>id_fab INTEGER REFERENCES fabrication ON DELETE CASCADE,
>
Hi,
I have the following tables :
CREATE TABLE tournee (
no_tournee SERIAL PRIMARY KEY);
CREATE TABLE fab_tournee (
id SERIAL PRIMARY KEY,
id_fab INTEGER REFERENCES fabrication ON DELETE CASCADE,
no_tournee INTEGER REFERENCES tournee ON DELETE CASCADE);
When I insert
Phillip,
> If Tom's not already on top of this, I'd be happy to help. There seem to be
> a few possibilities:
See my last e-mail. I'm not on -bugs, so my responses are delayed by the
moderation process.
> We can remove (3) by just doing a schema-only dump of the original DB. If
> this wor
Tom,
> Do you still have the original database available? The obvious route to
> finding the problem is to watch pg_dump in action and see why it misses
> that view. How do you feel about letting someone else have access to
> your system to do this? (Or get out a debugger and do it yourself..
