Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
21e0b7b8
Commit
21e0b7b8
authored
Jun 21, 2003
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Get rid of extraneous newline in PQendcopy error output (was causing
regression test diffs...).
parent
efc3a25b
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
30 additions
and
7 deletions
+30
-7
src/interfaces/libpq/fe-protocol2.c
src/interfaces/libpq/fe-protocol2.c
+21
-6
src/interfaces/libpq/fe-protocol3.c
src/interfaces/libpq/fe-protocol3.c
+9
-1
No files found.
src/interfaces/libpq/fe-protocol2.c
View file @
21e0b7b8
...
...
@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-protocol2.c,v 1.
2 2003/06/21 21:51:34
tgl Exp $
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-protocol2.c,v 1.
3 2003/06/21 23:25:38
tgl Exp $
*
*-------------------------------------------------------------------------
*/
...
...
@@ -1183,15 +1183,30 @@ pqEndcopy2(PGconn *conn)
}
/*
* Trouble. The worst case is that we've lost sync with the backend
* entirely due to application screwup of the copy in/out protocol. To
* recover, reset the connection (talk about using a sledgehammer...)
* Trouble. For backwards-compatibility reasons, we issue the error
* message as if it were a notice (would be nice to get rid of this
* silliness, but too many apps probably don't handle errors from
* PQendcopy reasonably). Note that the app can still obtain the
* error status from the PGconn object.
*/
PQclear
(
result
);
if
(
conn
->
errorMessage
.
len
>
0
)
{
/* We have to strip the trailing newline ... pain in neck... */
char
svLast
=
conn
->
errorMessage
.
data
[
conn
->
errorMessage
.
len
-
1
];
if
(
svLast
==
'\n'
)
conn
->
errorMessage
.
data
[
conn
->
errorMessage
.
len
-
1
]
=
'\0'
;
PGDONOTICE
(
conn
,
conn
->
errorMessage
.
data
);
conn
->
errorMessage
.
data
[
conn
->
errorMessage
.
len
-
1
]
=
svLast
;
}
PQclear
(
result
);
/*
* The worst case is that we've lost sync with the backend
* entirely due to application screwup of the copy in/out protocol. To
* recover, reset the connection (talk about using a sledgehammer...)
*/
PGDONOTICE
(
conn
,
libpq_gettext
(
"lost synchronization with server, resetting connection"
));
/*
...
...
src/interfaces/libpq/fe-protocol3.c
View file @
21e0b7b8
...
...
@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-protocol3.c,v 1.
2 2003/06/21 21:51:34
tgl Exp $
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-protocol3.c,v 1.
3 2003/06/21 23:25:38
tgl Exp $
*
*-------------------------------------------------------------------------
*/
...
...
@@ -1113,7 +1113,15 @@ pqEndcopy3(PGconn *conn)
* error status from the PGconn object.
*/
if
(
conn
->
errorMessage
.
len
>
0
)
{
/* We have to strip the trailing newline ... pain in neck... */
char
svLast
=
conn
->
errorMessage
.
data
[
conn
->
errorMessage
.
len
-
1
];
if
(
svLast
==
'\n'
)
conn
->
errorMessage
.
data
[
conn
->
errorMessage
.
len
-
1
]
=
'\0'
;
PGDONOTICE
(
conn
,
conn
->
errorMessage
.
data
);
conn
->
errorMessage
.
data
[
conn
->
errorMessage
.
len
-
1
]
=
svLast
;
}
PQclear
(
result
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment