úÎõşa®      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹Œ‘’“”•–—˜™š›œŸ ¡¢£¤¥¦§¨©ª«¬­ experimentalleon@melding-monads.comNone‹FLoFd is a Large Object (pseudo) File Descriptor. It is understood by * libpq but not by operating system calls. notification channel name 'process ID of notifying server process notification payload string ;Contains the information needed to cancel a command issued + through a particular database connection. *print output field headings and row count fill align the fields old brain dead format output HTML tables expand tables use pager for output if needed field separator "attributes for HTML table element HTML table caption  list of replacement field names !3The name of the source-code function reporting the  error. "2The line number of the source-code location where  the error was reported. #0The file name of the source-code location where  the error was reported. $0An indication of the context in which the error 0 occurred. Presently this includes a call stack 3 traceback of active procedural language functions 4 and internally-generated queries. The trace is one $ entry per line, most recent first. %*The text of a failed internally-generated 2 command. This could be, for example, a SQL query  issued by a PL/pgSQL function. & This is defined the same as the  ' field, but it is used when - the cursor position refers to an internally 4 generated command rather than the one submitted by  the client. The % field will ( always appear when this field appears. '1A string containing a decimal integer indicating / an error cursor position as an index into the 4 original statement string. The first character has 3 index 1, and positions are measured in characters  not bytes. (2Hint: an optional suggestion what to do about the 4 problem. This is intended to differ from detail in 3 that it offers advice (potentially inappropriate) 6 rather than hard facts. Might run to multiple lines. ),Detail: an optional secondary error message 6 carrying more detail about the problem. Might run to  multiple lines. *)The primary human-readable error message ' (typically one line). Always present. +3The SQLSTATE code for the error. The SQLSTATE code 4 identifies the type of error that has occurred; it 2 can be used by front-end applications to perform 1 specific operations (such as error handling) in 5 response to a particular database error. For a list 6 of the possible SQLSTATE codes, see Appendix A. This 2 field is not localizable, and is always present. ,3The severity; the field contents are ERROR, FATAL, 5 or PANIC (in an error message), or WARNING, NOTICE, 1 DEBUG, INFO, or LOG (in a notice message), or a / localized translation of one of these. Always  present. .A fatal error occurred. /A nonfatal error (a notice or  warning) occurred. 0 The server's response was not understood. 1"Copy In (to server) data transfer  started. 2Copy Out (from server) data  transfer started. 3Successful completion of a # command returning data (such as a  SELECT or SHOW). 4Successful completion of a  command returning no data. 5)The string sent to the server was empty. ;;8 encapsulates the result of a query (or more precisely, 5 of a single SQL command --- a query string given to  can A contain multiple commands and thus return multiple instances of  ;. =the connection is bad >$idle, in a failed transaction block ?#idle, in a valid transaction block @a command is in progress Acurrently idle CNegotiating SSL encryption. DNegotiating environment-driven  parameter settings. EReceived authentication; ! waiting for backend start-up to  finish. F(Waiting for a response from the server. G Connection OK; waiting to send. H#Waiting for connection to be made. I%The connection procedure has failed. JThe P is ready. PP+ encapsulates a connection to the backend. Q/Makes a new connection to the database server. CThis function opens a new database connection using the parameters @ taken from the string conninfo. Its nonblocking analogues are  R and U. DThe passed string can be empty to use all default parameters, or it 9 can contain one or more parameter settings separated by = whitespace. Each parameter setting is in the form keyword = E value. Spaces around the equal sign are optional. To write an empty E value or a value containing spaces, surround it with single quotes,  e.g., keyword = 'a value'+. Single quotes and backslashes within the / value must be escaped with a backslash, i.e., ' and \. RBMake a connection to the database server in a nonblocking manner. S7Allocate a Null Connection, which all libpq functions  should safely fail on. T-Test if a connection is the Null Connection. UIf R. succeeds, the next stage is to poll libpq so 7 that it can proceed with the connection sequence. Use f to  obtain the ®' of the socket underlying the database  connection. Loop thus: If U last returned  N-, wait until the socket is ready to read (as B indicated by select(), poll(), or similar system function). Then  call U again. Conversely, if U last  returned M+, wait until the socket is ready to write,  then call U again. If you have yet to call  U, i.e., just after the call to R , behave  as if it last returned M. Continue this loop until  U returns O, indicating the connection  procedure has failed, or L , indicating the connection has  been successfully made. V0Resets the communication channel to the server. BThis function will close the connection to the server and attempt C to reestablish a new connection to the same server, using all the A same parameters previously used. This might be useful for error + recovery if a working connection is lost. WHReset the communication channel to the server, in a nonblocking manner. X%To initiate a connection reset, call W. If it returns  ¯&, the reset has failed. If it returns °, poll the reset  using X1 in exactly the same way as you would create the  connection using U. Y%Closes the connection to the server. Note that the P must not be used again after Y  has been called. Z-Returns the database name of the connection. [)Returns the user name of the connection. \(Returns the password of the connection. ]0Returns the server host name of the connection. ^$Returns the port of the connection. _CReturns the command-line options passed in the connection request. `&Returns the status of the connection. BThe status can be one of a number of values. However, only two of A these are seen outside of an asynchronous connection procedure:  J and I. A good connection to the  database has the status J. A failed connection attempt  is signaled by status I. Ordinarily, an OK status  will remain so until Y%, but a communications failure might " result in the status changing to I prematurely. In ; that case the application could try to recover by calling V. See the entry for R and U with regards to ( other status codes that might be seen. a9Returns the current in-transaction status of the server. @4 is reported only when a query has been sent to the  server and not yet completed. b4Looks up a current parameter setting of the server. BCertain parameter values are reported by the server automatically 0 at connection startup or whenever their values  change. b" can be used to interrogate these D settings. It returns the current value of a parameter if known, or  ± if the parameter is not known. cInterrogates the frontend/backend protocol being used. AApplications might wish to use this to determine whether certain C features are supported. Currently, the possible values are 2 (2.0 B protocol), 3 (3.0 protocol), or zero (connection bad). This will ? not change after connection startup is complete, but it could B theoretically change during a connection reset. The 3.0 protocol A will normally be used when communicating with PostgreSQL 7.4 or E later servers; pre-7.4 servers support only protocol 2.0. (Protocol . 1.0 is obsolete and not supported by libpq.) d5Returns an integer representing the backend version. <Applications might use this to determine the version of the @ database server they are connected to. The number is formed by 8 converting the major, minor, and revision numbers into E two-decimal-digit numbers and appending them together. For example, B version 8.1.5 will be returned as 80105, and version 8.2 will be D returned as 80200 (leading zeroes are not shown). Zero is returned  if the connection is bad. eBReturns the error message most recently generated by an operation  on the connection. 2Nearly all libpq functions will set a message for e if 6 they fail. Note that by libpq convention, a nonempty e ; result can be multiple lines, and will include a trailing A newline. The result string should not be expected to remain the  same across operations on the P. f?Obtains the file descriptor number of the connection socket to @ the server. (This will not change during normal operation, but 1 could change during connection setup or reset.) gReturns the process ² of the backend server process  handling this connection. DThe backend PID is useful for debugging purposes and for comparison D to NOTIFY messages (which include the PID of the notifying backend C process). Note that the PID belongs to a process executing on the + database server host, not the local host! hReturns °4 if the connection authentication method required a + password, but none was available. Returns ¯ if not. BThis function can be applied after a failed connection attempt to 3 decide whether to prompt the user for a password. iReturns °0 if the connection authentication method used a  password. Returns ¯ if not. AThis function can be applied after either a failed or successful < connection attempt to detect whether the server demanded a  password. k:Submits a command to the server and waits for the result.  Returns a ; or possibly ±. A ; will generally B be returned except in out-of-memory conditions or serious errors ; such as inability to send the command to the server. If a ± * is returned, it should be treated like a . result. Use  e, to get more information about such errors. =It is allowed to include multiple SQL commands (separated by ? semicolons) in the command string. Multiple queries sent in a  single k4 call are processed in a single transaction, unless  there are explicit BEGIN/&COMMIT commands included in the query C string to divide it into multiple transactions. Note however that  the returned ;, structure describes only the result of the C last command executed from the string. Should one of the commands ? fail, processing of the string stops with it and the returned  ; describes the error condition. l?Submits a command to the server and waits for the result, with @ the ability to pass parameters separately from the SQL command  text. l is like k', but offers additional functionality: ? parameter values can be specified separately from the command E string proper, and query results can be requested in either text or  binary format. l' is supported only in protocol 3.0 and : later connections; it will fail when using protocol 2.0. The primary advantage of l over k is that parameter D values can be separated from the command string, thus avoiding the 8 need for tedious and error-prone quoting and escaping. Unlike k, l' allows at most one SQL command in the E given string. (There can be semicolons in it, but not more than one E nonempty command.) This is a limitation of the underlying protocol, C but has some usefulness as an extra defense against SQL-injection  attacks. BTip: Specifying parameter types via OIDs is tedious, particularly @ if you prefer not to hard-wire particular OID values into your B program. However, you can avoid doing so even in cases where the A server by itself cannot determine the type of the parameter, or B chooses a different type than you want. In the SQL command text, C attach an explicit cast to the parameter symbol to show what data " type you will send. For example: - SELECT * FROM mytable WHERE x = $1::bigint; > This forces parameter $1 to be treated as bigint, whereas by > default it would be assigned the same type as x. Forcing the E parameter type decision, either this way or by specifying a numeric D type OID, is strongly recommended when sending parameter values in D binary format, because binary format has less redundancy than text B format and so there is less chance that the server will detect a  type mismatch mistake for you. m@Submits a request to create a prepared statement with the given ' parameters, and waits for completion. m7 creates a prepared statement for later execution with  n1. This feature allows commands that will be used A repeatedly to be parsed and planned just once, rather than each  time they are executed. m# is supported only in protocol 3.0 > and later connections; it will fail when using protocol 2.0. BThe function creates a prepared statement named stmtName from the E query string, which must contain a single SQL command. stmtName can  be ""3 to create an unnamed statement, in which case any E pre-existing unnamed statement is automatically replaced; otherwise @ it is an error if the statement name is already defined in the C current session. If any parameters are used, they are referred to 7 in the query as $1, $2, etc. paramTypes specifies, by 6, the C data types to be assigned to the parameter symbols. If paramTypes  is ±6, or any particular element in the array is zero, the D server assigns a data type to the parameter symbol in the same way D it would do for an untyped literal string. Also, the query can use : parameter symbols with numbers higher than the length of > paramTypes; data types will be inferred for these symbols as  well. (See o# for a means to find out what data  types were inferred.) As with k, the result is normally a ; whose contents , indicate server-side success or failure. A ± result = indicates out-of-memory or inability to send the command at  all. Use e, to get more information about such errors. !Prepared statements for use with n can also be created + by executing SQL PREPARE statements. (But m is more : flexible since it does not require parameter types to be ? pre-specified.) Also, although there is no libpq function for D deleting a prepared statement, the SQL DEALLOCATE statement can be  used for that purpose. n;Sends a request to execute a prepared statement with given ' parameters, and waits for the result. n is like l!, but the command to be executed D is specified by naming a previously-prepared statement, instead of B giving a query string. This feature allows commands that will be A used repeatedly to be parsed and planned just once, rather than D each time they are executed. The statement must have been prepared $ previously in the current session. n is supported only @ in protocol 3.0 and later connections; it will fail when using  protocol 2.0.  The parameters are identical to l, except that the name E of a prepared statement is given instead of a query string, and the A paramTypes parameter is not present (it is not needed since the  prepared statement'.s parameter types were determined when it was  created). o<Submits a request to obtain information about the specified / prepared statement, and waits for completion. o- allows an application to obtain information ( about a previously prepared statement. o is D supported only in protocol 3.0 and later connections; it will fail  when using protocol 2.0. DstmtName can be empty to reference the unnamed statement, otherwise D it must be the name of an existing prepared statement. On success,  a ; with status 4 is returned. The functions  † and ‡ can be applied to this ; to obtain E information about the parameters of the prepared statement, and the  functions w, z, , etc provide information 5 about the result columns (if any) of the statement. p<Submits a request to obtain information about the specified # portal, and waits for completion. p3 allows an application to obtain information about A a previously created portal. (libpq does not provide any direct A access to portals, but you can use this function to inspect the D properties of a cursor created with a DECLARE CURSOR SQL command.)  p- is supported only in protocol 3.0 and later 4 connections; it will fail when using protocol 2.0. CportalName can be empty to reference the unnamed portal, otherwise : it must be the name of an existing portal. On success, a ;  with status 4 is returned. The functions w,  z, , etc can be applied to the ; to obtain > information about the result columns (if any) of the portal. q*Returns the result status of the command. r Converts the - returned by q into a : string describing the status code. The caller should not  free the result. sBReturns the error message most recently generated by an operation  on the connection. tAFrees the memory associated with a result. Note that using this C function correctly is especially tricky; you need to ensure that D no references to the result. This means no references to a value  returned by ‚., no references hiding inside an unevaluated D thunk, etc. Improper use of this function is likely to cause a H segfault. Also, the use of this function is not strictly necessary; F the memory will get freed by the garbage collector when there are no  more references to the result. u0Returns an individual field of an error report. ?fieldcode is an error field identifier; see the symbols listed  below. ±0 is returned if the PGresult is not an error or @ warning result, or does not include the specified field. Field 6 values will normally not include a trailing newline. BThe client is responsible for formatting displayed information to = meet its needs; in particular it should break long lines as B needed. Newline characters appearing in the error message fields 9 should be treated as paragraph breaks, not line breaks. DErrors generated internally by libpq will have severity and primary > message, but typically no other fields. Errors returned by a D pre-3.0-protocol server will include severity and primary message, 6 and sometimes a detail message, but no other fields. /Note that error fields are only available from ; objects,  not P+ objects; there is no errorField function. vAReturns the number of rows (tuples) in the query result. Because D it returns an integer result, large result sets might overflow the + return value on 32-bit operating systems. w@Returns the number of columns (fields) in each row of the query  result. z2Returns the column name associated with the given  $ number. Column numbers start at 0. {AReturns the column number associated with the given column name. |=Returns the OID of the table from which the given column was % fetched. Column numbers start at 0. }BReturns the column number (within its table) of the column making C up the specified query result column. Query-result column numbers 5 start at 0, but table columns have nonzero numbers. ~ Returns the 8. of the given column. Column numbers start at  0. 7Returns the data type associated with the given column  number. The 6, returned is the internal OID number of the " type. Column numbers start at 0. ?You can query the system table pg_type to obtain the names and E properties of the various data types. The OIDs of the built-in data " types are defined in the file srcincludecatalog/pg_type.h in the  source tree. €BReturns the type modifier of the column associated with the given + column number. Column numbers start at 0. =The interpretation of modifier values is type-specific; they C typically indicate precision or size limits. The value -1 is used  to indicate no information available. Most data types do not use 2 modifiers, in which case the value is always -1. BReturns the size in bytes of the column associated with the given + column number. Column numbers start at 0. ; returns the space allocated for this column in a database + row, in other words the size of the server' s internal A representation of the data type. (Accordingly, it is not really C very useful to clients.) A negative value indicates the data type  is variable-length. ‚?Returns a single field value of one row of a PGresult. Row and  column numbers start at 0. #For convenience, this binding uses „ and … to  help construct the result.  Note: The  ByteString. returned holds a reference to the Result. As < long as ByteString is live, the Result will not be garbage  collected. ƒ returns a copy of the data. ƒ7Returns a copy of a single field value of one row of a . PGresult. Row and column numbers start at 0. #For convenience, this binding uses „ and … to  help construct the result. „@Tests a field for a null value. Row and column numbers start at  0. …=Returns the actual length of a field value in bytes. Row and  column numbers start at 0. CThis is the actual data length for the particular data value, that * is, the size of the object pointed to by ‚. For text data @ format this is the same as strlen(). For binary format this is 9 essential information. Note that one should not rely on  to  obtain the actual data length. †:Returns the number of parameters of a prepared statement. ;This function is only useful when inspecting the result of E PQdescribePrepared. For other types of queries it will return zero. ‡1Returns the data type of the indicated statement * parameter. Parameter numbers start at 0. ;This function is only useful when inspecting the result of  o2. For other types of queries it will return zero. ‰9Returns the command status tag from the SQL command that  generated the PGresult. DCommonly this is just the name of the command, but it might include 7 additional data such as the number of rows processed. Š8Returns the number of rows affected by the SQL command. =This function returns a string containing the number of rows 2 affected by the SQL statement that generated the ;. This @ function can only be used following the execution of a SELECT, ? CREATE TABLE AS, INSERT, UPDATE, DELETE, MOVE, FETCH, or COPY ? statement, or an EXECUTE of a prepared query that contains an D INSERT, UPDATE, or DELETE statement. If the command that generated  the ; was anything else, Š returns an empty  string. ‹ Returns the 60 of the inserted row, if the SQL command was an E INSERT that inserted exactly one row into a table that has OIDs, or < a EXECUTE of a prepared query containing a suitable INSERT - statement. Otherwise, this function returns ±. This  function will also return ± if the table affected by the ) INSERT statement does not contain OIDs. Œ?Escapes a string for use within an SQL command. This is useful 8 when inserting data values as literal constants in SQL D commands. Certain characters (such as quotes and backslashes) must D be escaped to prevent them from being interpreted specially by the  SQL parser. @Escapes binary data for use within an SQL command with the type  bytea. As with Œ#, this is only used when inserting + data directly into an SQL command string.  Converts a  ByteString+ representation of binary data into binary  data - the reverse of PQescapeByteaConn. This is needed when E retrieving bytea data in text format, but not when retrieving it in  binary format. >The parameter points to a string such as might be returned by  ‚! when applied to a bytea column.  converts ? this string representation into its binary representation. It  returns a  ByteString, or ± on error. .This conversion is not exactly the inverse of , * because the string is not expected to be escaped when received  from ‚0. In particular this means there is no need for 5 string quoting considerations, and so no need for a P  parameter. 8Submits a command to the server without waiting for the  result(s). °- is returned if the command was successfully  dispatched and ¯ if not (in which case, use e to * get more information about the failure). @Submits a command and separate parameters to the server without  waiting for the result(s). ‘>Sends a request to create a prepared statement with the given - parameters, without waiting for completion. ’;Sends a request to execute a prepared statement with given 0 parameters, without waiting for the result(s). “<Submits a request to obtain information about the specified 5 prepared statement, without waiting for completion. #This is an asynchronous version of o : it returns  °- if it was able to dispatch the request, and ¯ if $ not. After a successful call, call • to obtain the  results. The function'(s parameters are handled identically to  o. Like o, it will not work on  2.0-protocol connections. ”<Submits a request to obtain information about the specified ) portal, without waiting for completion. #This is an asynchronous version of p : it returns  °- if it was able to dispatch the request, and ¯ if $ not. After a successful call, call • to obtain the  results. The function'(s parameters are handled identically to  p. Like p, it will not work on  2.0-protocol connections. •'Waits for the next result from a prior ,  , ‘, or ’ call, and E returns it. A null pointer is returned when the command is complete $ and there will be no more results. –3If input is available from the server, consume it. – normally returns ° indicating no error, but  returns ¯2 if there was some kind of trouble (in which case  e6 can be consulted). Note that the result does not say > whether any input data was actually collected. After calling  –, the application can check — and/or  $ to see if their state has changed. —BReturns True if a command is busy, that is, getResult would block C waiting for input. A False return indicates that getResult can be ( called with assurance of not blocking. —7 will not itself attempt to read data from the server;  therefore –* must be invoked first, or the busy state  will never end. ˜/Sets the nonblocking status of the connection. ™8Returns the blocking status of the database connection. š@Attempts to flush any queued output data to the server. Returns  0 if successful (or if the send queue is empty),  " if it failed for some reason, or   if it B was unable to send all the data in the send queue yet (this case 3 can only occur if the connection is nonblocking). ›>Creates a data structure containing the information needed to C cancel a command issued through a particular database connection. › creates a   object given a P . It will  return ±- if the given conn is an invalid connection. œ;Requests that the server abandon processing of the current  command. The return value is 'Right ()' if the cancel request was % successfully dispatched and if not, 'Left B.ByteString' containing & an error message explaining why not. CSuccessful dispatch is no guarantee that the request will have any @ effect, however. If the cancellation is effective, the current A command will terminate early and return an error result. If the > cancellation fails (say, because the server was already done B processing the command), then there will be no visible result at  all. 7Returns the next notification from a list of unhandled > notification messages received from the server. It returns a  ±/ if there are no pending notifications. Once a B notification is returned from notifies, it is considered handled 5 and will be removed from the list of notifications. Returns the client encoding. ŸSets the client encoding.  1Determines the verbosity of messages returned by e  and s.  ( sets the verbosity mode, returning the  connection's previous setting. In  mode, returned B messages include severity, primary text, and position only; this ? will normally fit on a single line. The default mode produces C messages that include the above plus any detail, hint, or context / fields (these might span multiple lines). The  mode @ includes all available fields. Changing the verbosity does not 5 affect the messages available from already-existing ; * objects, only subsequently-created ones. ¡HCreates a new large object, returns the Object ID of the newly created  object. ¢ACreates a new large object with a particular Object ID. Returns  ±< if the requested Object ID is already in use by some other $ large object or other failure. If j is used as a parameter,  then ¢ will assign an unused 6. £CImports an operating system file as a large object. Note that the H file is read by the client interface library, not by the server; so it D must exist in the client file system and be readable by the client  application. ¤BImports an operating system file as a large object with the given & Object ID. Combines the behavior of £ and ¢ ¥@Exports a large object into a operating system file. Note that F the file is written by the client interface library, not the server.  Returns 'Just ()' on success, ± on failure. ¦JOpens an existing large object for reading or writing. The Oid specifies I the large object to open. A large object cannot be opened before it is B created. A large object descriptor is returned for later use in ¨,  §, ©, ª, and ¬!. The descriptor is only valid < for the duration of the current transation. On failure, ± is  returned. 2The server currently does not distinguish between ³ and  ´5; write-only modes are not enforced. However there % is a significant difference between µ and the other modes:  with µ8 you cannot write on the descriptor, and the data read F from it will reflect the contents of the large object at the time of / the transaction snapshot that was active when ¦ was executed, J regardless of later writes by this or other transactions. Reading from  a descriptor opened in ³, ´, or ¶ G returns data that reflects all writes of other committed transactions H as well as the writes of the current transaction. This is similar to  the behavior of REPEATABLE READ versus READ COMMITTED transaction  modes for ordinary SQL SELECT commands. §loWrite conn fd buf writes the bytestring buf to the large object  descriptor fd5. The number of bytes actually written is returned.  In the event of an error, ± is returned. ¨loRead conn fd len reads up to len bytes from the large object  descriptor fd. In the event of an error, ± is returned. ©;Changes the current read or write location associated with D a large object descriptor. The return value is the new location  pointer, or ± on error. ªIObtains the current read or write location of a large object descriptor. «FTruncates a large object to a given length. If the length is greater H than the current large object, then the large object is extended with  null bytes. ('\x00')  The file offest is not changed. «> is new as of PostgreSQL 8.3; if this function is run against 2 an older server version, it will fail and return ± ¬ECloses a large object descriptor. Any large object descriptors that G remain open at the end of a transaction will be closed automatically. ­*Removes a large object from the database. ³  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQConnection Info RConnection Info STUVWXYZ[\]^_`ab paramName cdefghijk connection  statement result l connection  statement  parameters result format result m connection  stmtName query  paramTypes result n connection  stmtName  parameters result format result o stmtName p portalName qrstuvwxyz{|}~€‚ƒ„…†‡ param_number ˆ‰Š‹Œ‘’“ stmtName ” portalName •–—˜™š›œŸ ¡¢£¤¥¦§¨©ª«¬­·¸¹º»®  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹Œ‘’“”•–—˜™š›œŸ ¡¢£¤¥¦§¨©ª«¬­®PQRUSTVWXKONMLYZ[\]^_BJIHGFEDC`<A@?>=abcdefghi;k8:967jlmnop-543210/.qrs ,+*)('&%$#"!utvwyxz{|}~€‚ƒ„…†‡ˆ‰Š‹Œ‘’“”•–—˜™  š ›œ Ÿ ¡¢£¤¥¦§¨©ª«¬­s    ,+*)('&%$#"!-543210/.678:9;<A@?>=BJIHGFEDCKONMLPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹Œ‘’“”•–—˜™š›œŸ ¡¢£¤¥¦§¨©ª«¬­·¸¹º»¼      !"#$%&'()*+,-./01234456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹Œ‘’“”•–—˜™š›œŸ ¡¢£¤¥¦§¨©ª«¬­®¯°®¯±«²³«¬´«µ¶«µ·«µ¸«µ¹º»¼½¾¿postgresql-libpq-0.7Database.PostgreSQL.LibPQLoFd Verbosity ErrorsVerbose ErrorsDefault ErrorsTerseNotify notifyRelname notifyBePid notifyExtraCancel FlushStatus FlushWriting FlushFailedFlushOkPrintOptpoHeaderpoAlign poStandardpoHtml3 poExpandedpoPager poFieldSep poTableOpt poCaption poFieldNameRowColumnCol FieldCodeDiagSourceFunctionDiagSourceLineDiagSourceFile DiagContextDiagInternalQueryDiagInternalPositionDiagStatementPositionDiagMessageHintDiagMessageDetailDiagMessagePrimary DiagSqlstate DiagSeverity ExecStatus FatalError NonfatalError BadResponseCopyInCopyOutTuplesOk CommandOk EmptyQueryOidFormatBinaryTextResultTransactionStatus TransUnknown TransInError TransInTrans TransActive TransIdle ConnStatusConnectionSSLStartupConnectionSetEnvConnectionAuthOkConnectionAwaitingResponseConnectionMadeConnectionStarted ConnectionBad ConnectionOk PollingStatus PollingOkPollingWritingPollingReading PollingFailed Connection connectdb connectStartnewNullConnectionisNullConnection connectPollreset resetStart resetPollfinishdbuserpasshostportoptionsstatustransactionStatusparameterStatusprotocolVersion serverVersion errorMessagesocket backendPIDconnectionNeedsPasswordconnectionUsedPassword invalidOidexec execParamsprepare execPrepareddescribePrepareddescribePortal resultStatus resStatusresultErrorMessageunsafeFreeResultresultErrorFieldntuplesnfieldstoColumntoRowfnamefnumberftable ftablecolfformatftypefmodfsizegetvalue getvalue' getisnull getlengthnparams paramtypedefaultPrintOpt cmdStatus cmdTuplesoidValueescapeStringConnescapeByteaConn unescapeBytea sendQuerysendQueryParams sendPreparesendQueryPreparedsendDescribePreparedsendDescribePortal getResult consumeInputisBusysetnonblocking isnonblockingflush getCancelcancelnotifiesclientEncodingsetClientEncodingsetErrorVerbosityloCreatloCreateloImportloImportWithOidloExportloOpenloWriteloReadloSeekloTell loTruncateloCloseloUnlinkbaseSystem.Posix.TypesFdghc-prim GHC.TypesFalseTrue Data.MaybeNothingCPid GHC.IO.IOMode WriteMode ReadWriteModeReadMode AppendMode$fEnumVerbosity$fStorableNotify$fStorablePrintOpt$fEnumFieldCode$fEnumExecStatus