mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

When under postmaster, bogus arguments should cause proc_exit(0) not

Browse Source 
proc_exit(1).  Unless you think a system-wide restart is an appropriate
response to bogus PGOPTIONS, that is.
This commit is contained in:
Tom Lane 2001-02-24 02:04:51 +00:00
parent 2b0f8ae009
commit f1e0044ba3
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/tcop/postgres.c
View File

@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/tcop/postgres.c,v 1.207 2001/02/18 04:28:31 tgl Exp $
* $Header: /cvsroot/pgsql/src/backend/tcop/postgres.c,v 1.208 2001/02/24 02:04:51 tgl Exp $
*
* NOTES
* this is the "main" module of the postgres backend and
@ -1537,7 +1537,7 @@ PostgresMain(int argc, char *argv[], int real_argc, char *real_argv[], const cha
if (errs || argc != optind || DBName == NULL)
{
fprintf(stderr, "%s: invalid command line arguments\nTry -? for help.\n", argv[0]);
proc_exit(1);
proc_exit(0); /* not 1, that causes system-wide restart... */
}
pq_init(); /* initialize libpq at backend startup */
whereToSendOutput = Remote;
@ -1680,7 +1680,7 @@ PostgresMain(int argc, char *argv[], int real_argc, char *real_argv[], const cha
if (!IsUnderPostmaster)
{
puts("\nPOSTGRES backend interactive interface ");
puts("$Revision: 1.207 $ $Date: 2001/02/18 04:28:31 $\n");
puts("$Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $\n");
}
/*