[tag=CC] | [□ | □]
[tag=CC] | [□=□ | □]
[tag=CC] | [□ & □ | □]
It 's up to the call handler to fetch the pg_proc entry and to analyze the argument and return types of the called procedure . Note that if the left and right data types are different , neither of these operators is the same as either SORT operator . Note : Neither sequential scans nor nested-loop joins can be disabled completely ; the - fs and - fn options simply discourage the optimizer from using those plan types if it has any other alternative . Since there is no problem overloading SQL functions , you can define a set of C functions with different names and then define a set of identically-named SQL function wrappers that take the appropriate argument types and call the matching C function . These operators must be named ' <' and '> ' ; you do not have any choice in the matter , since there is no provision for specifying them explicitly . There must be ' <' and '> ' ordering operators having the same left and right input datatypes as the mergejoinable operator itself . Any such known problems and their solutions will be posted in ftp://ftp.postgresql.org/pub/INSTALL.Create the Postgres superuser account ( postgres is commonly used ) if it does not already exist.The owner of the Postgres files can be any unprivileged user account . In that case you 'll need to figure out which one to use and run configure again , this time giving the - - with-template = TEMPLATE option to make the right file be chosen . If the pg_dumpall command seems to take a long time and you think it might have died , then , from another terminal , type $ ls - l db.out several times to see if the size of the file is growing .