doc-savepoint-explicitrelease.patch

application/octet-stream

Filename: doc-savepoint-explicitrelease.patch

Type: application/octet-stream

Part: 0

Message: Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT

Patch

Same data as JSON: GET /api/v1/attachments/:id/patch the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes. API reference →

Format: unified

File	+	−
doc/src/sgml/ref/savepoint.sgml	0	0

diff --git a/doc/src/sgml/ref/savepoint.sgml b/doc/src/sgml/ref/savepoint.sgml
index c327b6b..90d3895 100644
*** a/doc/src/sgml/ref/savepoint.sgml
--- b/doc/src/sgml/ref/savepoint.sgml
*************** COMMIT;
*** 115,124 ****
     SQL requires a savepoint to be destroyed automatically when another
     savepoint with the same name is established.  In
     <productname>PostgreSQL</>, the old savepoint is kept, though only the more
!    recent one will be used when rolling back or releasing.  (Releasing the
!    newer savepoint will cause the older one to again become accessible to
!    <command>ROLLBACK TO SAVEPOINT</> and <command>RELEASE SAVEPOINT</>.)
!    Otherwise, <command>SAVEPOINT</command> is fully SQL conforming.
    </para>
   </refsect1>
  
--- 115,125 ----
     SQL requires a savepoint to be destroyed automatically when another
     savepoint with the same name is established.  In
     <productname>PostgreSQL</>, the old savepoint is kept, though only the more
!    recent one will be used when rolling back or releasing.  (Explicitly
!    releasing the newer savepoint with <command>RELEASE SAVEPOINT</> will cause
!    the older one to again become accessible to <command>ROLLBACK TO SAVEPOINT</>
!    and <command>RELEASE SAVEPOINT</>.) Otherwise, <command>SAVEPOINT</command> is
!    fully SQL conforming.
    </para>
   </refsect1>