rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/src/include/libpq/be-fsstubs.h

46 lines
1.2 KiB
C
Raw Normal View History

Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
/*-------------------------------------------------------------------------
*
Change my-function-name-- to my_function_name, and optimizer renames.
1999-02-14 00:22:53 +01:00
* be-fsstubs.h
Massive commit to run PGINDENT on all *.c and *.h files.
1997-09-07 07:04:48 +02:00
*
Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
*
*
* Copyright (c) 1994, Regents of the University of California
*
Clean up memory leaks in LO operations by freeing LO's private memory context at transaction commit or abort.
1999-06-01 00:53:59 +02:00
* $Id: be-fsstubs.h,v 1.9 1999/05/31 22:53:58 tgl Exp $
Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
*
*-------------------------------------------------------------------------
*/
Massive commit to run PGINDENT on all *.c and *.h files.
1997-09-07 07:04:48 +02:00
#ifndef BE_FSSTUBS_H
#define BE_FSSTUBS_H
Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
Rename LOread() and LOwrite() to be lower case to allow use in case-insensitive SQL. Define LOread() and LOwrite() as macros to avoid having to update calls everywhere.
1997-05-06 09:14:34 +02:00
/* Redefine names LOread() and LOwrite() to be lowercase to allow calling
Massive commit to run PGINDENT on all *.c and *.h files.
1997-09-07 07:04:48 +02:00
* using the new v6.1 case-insensitive SQL parser. Define macros to allow
* the existing code to stay the same. - tgl 97/05/03
Rename LOread() and LOwrite() to be lower case to allow use in case-insensitive SQL. Define LOread() and LOwrite() as macros to avoid having to update calls everywhere.
1997-05-06 09:14:34 +02:00
*/
#define LOread(f,l) loread(f,l)
#define LOwrite(f,b) lowrite(f,b)
Used modified version of indent that understands over 100 typedefs.
1997-09-08 23:56:23 +02:00
extern Oid lo_import(text *filename);
extern int4 lo_export(Oid lobjId, text *filename);
Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.
1997-09-08 04:41:22 +02:00
extern Oid lo_creat(int mode);
Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.
1997-09-08 04:41:22 +02:00
extern int lo_open(Oid lobjId, int mode);
extern int lo_close(int fd);
extern int lo_read(int fd, char *buf, int len);
extern int lo_write(int fd, char *buf, int len);
extern int lo_lseek(int fd, int offset, int whence);
extern int lo_tell(int fd);
extern int lo_unlink(Oid lobjId);
Postgres95 1.01 Distribution - Virgin Sources
1996-07-09 08:22:35 +02:00
Rename LOread() and LOwrite() to be lower case to allow use in case-insensitive SQL. Define LOread() and LOwrite() as macros to avoid having to update calls everywhere.
1997-05-06 09:14:34 +02:00
extern struct varlena *loread(int fd, int len);
Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.
1997-09-08 04:41:22 +02:00
extern int lowrite(int fd, struct varlena * wbuf);
Rename LOread() and LOwrite() to be lower case to allow use in case-insensitive SQL. Define LOread() and LOwrite() as macros to avoid having to update calls everywhere.
1997-05-06 09:14:34 +02:00
Theses buffer leaks are caused by indexes that are kept open between calls. Outside a transaction, the backend detects them as buffer leaks; it sends a NOTICE, and frees them. This sometimes cause a segmentation fault (at least on Linux). These indexes are initialized on the first lo_read/lo_write/lo_tell call, and (normally) closed on a lo_close call. Thus the buffer leaks appear when lo direct access functions are used, and not with lo_import/lo_export functions (libpq version calls lo_close before ending the command, and the backend version uses another path). The included patches (against recent snapshot, and against 6.3.2) cause indexes to be closed on transaction end (that is on explicit 'END' statment, or on command termination outside trasaction blocks), thus preventing the buffer leaks while increasing performance inside transactions. Some (all?) 'classic' memory leaks are also removed. I hope it will be ok. --- Pascal ANDRE, graduated from Ecole Centrale Paris andre@via.ecp.fr
1998-07-21 06:17:30 +02:00
/*
* Added for buffer leak prevention [ Pascal Andr<EFBFBD> <andre@via.ecp.fr> ]
*/
Clean up memory leaks in LO operations by freeing LO's private memory context at transaction commit or abort.
1999-06-01 00:53:59 +02:00
extern void lo_commit(bool isCommit);
Theses buffer leaks are caused by indexes that are kept open between calls. Outside a transaction, the backend detects them as buffer leaks; it sends a NOTICE, and frees them. This sometimes cause a segmentation fault (at least on Linux). These indexes are initialized on the first lo_read/lo_write/lo_tell call, and (normally) closed on a lo_close call. Thus the buffer leaks appear when lo direct access functions are used, and not with lo_import/lo_export functions (libpq version calls lo_close before ending the command, and the backend version uses another path). The included patches (against recent snapshot, and against 6.3.2) cause indexes to be closed on transaction end (that is on explicit 'END' statment, or on command termination outside trasaction blocks), thus preventing the buffer leaks while increasing performance inside transactions. Some (all?) 'classic' memory leaks are also removed. I hope it will be ok. --- Pascal ANDRE, graduated from Ecole Centrale Paris andre@via.ecp.fr
1998-07-21 06:17:30 +02:00
OK, folks, here is the pgindent output.
1998-09-01 06:40:42 +02:00
#endif /* BE_FSSTUBS_H */