codekingpro/portable-devtools

1<?xml version="1.0" encoding="UTF-8" standalone="no"?>2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>75.3. BKI File Format</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="system-catalog-initial-data.html" title="75.2. System Catalog Initial Data" /><link rel="next" href="bki-commands.html" title="75.4. BKI Commands" /></head><body id="docContent" class="container-fluid col-10"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">75.3. <acronym class="acronym">BKI</acronym> File Format</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="system-catalog-initial-data.html" title="75.2. System Catalog Initial Data">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="bki.html" title="Chapter 75. System Catalog Declarations and Initial Contents">Up</a></td><th width="60%" align="center">Chapter 75. System Catalog Declarations and Initial Contents</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 16.3 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="bki-commands.html" title="75.4. BKI Commands">Next</a></td></tr></table><hr /></div><div class="sect1" id="BKI-FORMAT"><div class="titlepage"><div><div><h2 class="title" style="clear: both">75.3. <acronym class="acronym">BKI</acronym> File Format <a href="#BKI-FORMAT" class="id_link">#</a></h2></div></div></div><p>3   This section describes how the <span class="productname">PostgreSQL</span>4   backend interprets <acronym class="acronym">BKI</acronym> files.  This description5   will be easier to understand if the <code class="filename">postgres.bki</code>6   file is at hand as an example.7  </p><p>8   <acronym class="acronym">BKI</acronym> input consists of a sequence of commands.  Commands are made up9   of a number of tokens, depending on the syntax of the command.10   Tokens are usually separated by whitespace, but need not be if11   there is no ambiguity.  There is no special command separator; the12   next token that syntactically cannot belong to the preceding13   command starts a new one.  (Usually you would put a new command on14   a new line, for clarity.)  Tokens can be certain key words, special15   characters (parentheses, commas, etc.), identifiers, numbers, or16   single-quoted strings.  Everything is case sensitive.17  </p><p>18   Lines starting with <code class="literal">#</code> are ignored.19  </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="system-catalog-initial-data.html" title="75.2. System Catalog Initial Data">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="bki.html" title="Chapter 75. System Catalog Declarations and Initial Contents">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bki-commands.html" title="75.4. BKI Commands">Next</a></td></tr><tr><td width="40%" align="left" valign="top">75.2. System Catalog Initial Data </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 16.3 Documentation">Home</a></td><td width="40%" align="right" valign="top"> 75.4. <acronym class="acronym">BKI</acronym> Commands</td></tr></table></div></body></html>