aboutsummaryrefslogtreecommitdiff
path: root/src/backend/regex/regc_lex.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-10-22 01:02:22 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-10-22 01:02:22 +0000
commitf1c87830b5e34af0a39a8252b54c4cb216651437 (patch)
tree6465db85c52fbd3bf5c792cf4a11e198a7f2d804 /src/backend/regex/regc_lex.c
parent1ea47dd8cbcb485a06676f12a36244270e18e192 (diff)
downloadpostgresql-f1c87830b5e34af0a39a8252b54c4cb216651437.tar.gz
postgresql-f1c87830b5e34af0a39a8252b54c4cb216651437.zip
Add a useless return statement to suppress a warning seen with some
versions of gcc (I'm seeing it with Apple's gcc 4.0.1). I think the reason we did not see this before was that the assert() macros in the regex code were all no-ops till recently.
Diffstat (limited to 'src/backend/regex/regc_lex.c')
-rw-r--r--src/backend/regex/regc_lex.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/regex/regc_lex.c b/src/backend/regex/regc_lex.c
index df45701e5aa..e5c83d87147 100644
--- a/src/backend/regex/regc_lex.c
+++ b/src/backend/regex/regc_lex.c
@@ -28,7 +28,7 @@
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
* ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
- * $PostgreSQL: pgsql/src/backend/regex/regc_lex.c,v 1.5 2005/10/15 02:49:24 momjian Exp $
+ * $PostgreSQL: pgsql/src/backend/regex/regc_lex.c,v 1.6 2007/10/22 01:02:22 tgl Exp $
*
*/
@@ -1071,6 +1071,7 @@ brenext(struct vars * v,
}
assert(NOTREACHED);
+ return 0;
}
/*