Skip to main content
Ctrl+K

Tantor Basic Edition 16.8 documentation

Table of contents:

  • Preface
    • 1.  What Is Tantor BE?
    • 2. A Brief History of PostgreSQL
    • 3. What are the differences between Tantor BE 16 and PostgreSQL 16
    • 4. Conventions
    • 5. Bug Reporting Guidelines
  • Part I. Tutorial
    • Chapter 1. Synopsis
    • Chapter 2. The SQL Language
    • Chapter 3. Advanced Features
  • Part II. The SQL Language
    • Chapter 4. SQL Syntax
    • Chapter 5. Data Definition
    • Chapter 6. Data Manipulation
    • Chapter 7. Queries
    • Chapter 8. Data Types
    • Chapter 9. Functions and Operators
    • Chapter 10. Type Conversion
    • Chapter 11. Indexes
    • Chapter 12. Full Text Search
    • Chapter 13. Concurrency Control
    • Chapter 14. Performance Tips
    • Chapter 15. Parallel Query
  • Part III. Server Administration
    • Chapter 16. Installation from Binaries
    • Chapter 17. Server Setup and Operation
    • Chapter 18. Server Configuration
    • Chapter 19. Client Authentication
    • Chapter 20. Database Roles
    • Chapter 21. Managing Databases
    • Chapter 22. Localization
    • Chapter 23. Routine Database Maintenance Tasks
    • Chapter 24. Backup and Restore
    • Chapter 25. High Availability, Load Balancing, and Replication
    • Chapter 26. Monitoring Database Activity
    • Chapter 27. Monitoring Disk Usage
    • Chapter 28. Reliability and the Write-Ahead Log
    • Chapter 29. Logical Replication
    • Chapter 30. Just-in-Time Compilation (JIT)
  • Part IV. Client Interfaces
    • Chapter 31. libpq — C Library
    • Chapter 32. Large Objects
    • Chapter 33. ECPG — Embedded SQL in C
    • Chapter 34. The Information Schema
  • Part V. Server Programming
    • Chapter 35. Extending SQL
    • Chapter 36. Triggers
    • Chapter 37. Event Triggers
    • Chapter 38. The Rule System
    • Chapter 39. Procedural Languages
    • Chapter 40. PL/pgSQL — SQL Procedural Language
    • Chapter 41. PL/Tcl — Tcl Procedural Language
    • Chapter 42. PL/Perl — Perl Procedural Language
    • Chapter 43. PL/Python — Python Procedural Language
    • Chapter 44. Server Programming Interface
    • Chapter 45. Background Worker Processes
    • Chapter 46. Logical Decoding
    • Chapter 47. Replication Progress Tracking
    • Chapter 48. Archive Modules
  • Part VI. Reference
    • SQL Commands
    • PostgreSQL Client Applications
    • PostgreSQL Server Applications
  • Part VII. Internals
    • Chapter 49. Overview of PostgreSQL Internals
    • Chapter 50. System Catalogs
    • Chapter 51. System Views
    • Chapter 52. Frontend/Backend Protocol
    • Chapter 53. PostgreSQL Coding Conventions
    • Chapter 54. Native Language Support
    • Chapter 55. Writing a Procedural Language Handler
    • Chapter 56. Writing a Foreign Data Wrapper
    • Chapter 57. Writing a Table Sampling Method
    • Chapter 58. Writing a Custom Scan Provider
    • Chapter 59. Genetic Query Optimizer
    • Chapter 60. Table Access Method Interface Definition
    • Chapter 61. Index Access Method Interface Definition
    • Chapter 62. Generic WAL Records
    • Chapter 63. Custom WAL Resource Managers
    • Chapter 64. B-Tree Indexes
    • Chapter 65. GiST Indexes
    • Chapter 66. SP-GiST Indexes
    • Chapter 67. GIN Indexes
    • Chapter 68. BRIN Indexes
    • Chapter 69. Hash Indexes
    • Chapter 70. Database Physical Storage
    • Chapter 71. Transaction Processing
    • Chapter 72. System Catalog Declarations and Initial Contents
    • Chapter 73. How the Planner Uses Statistics
    • Chapter 74. Backup Manifest Format
  • Part VIII. Appendixes
    • Appendix A. Tantor BE Error Codes
    • Appendix B. Date/Time Support
    • Appendix C. SQL Key Words
    • Appendix D. SQL Conformance
    • Appendix E. Release Notes
    • Appendix F. Additional Supplied Modules and Extensions
    • Appendix G. Additional Supplied Programs
    • Appendix H. Additional External Modules
    • Appendix I. External Projects
    • Appendix J. Tantor BE Limits
    • Appendix K. Acronyms
    • Appendix L. Glossary
    • Appendix M. Color Support
    • Appendix N. Obsolete or Renamed Features
  • Bibliography
  • Index

dblink_build_sql_insert

dblink_build_sql_insert#

dblink_build_sql_insert
dblink_build_sql_insert
Prev UpF.13. dblink — connect to other PostgreSQL databasesHome Next

dblink_build_sql_insert

dblink_build_sql_insert — builds an INSERT statement using a local tuple, replacing the primary key field values with alternative supplied values

Synopsis

dblink_build_sql_insert(text relname,
                        int2vector primary_key_attnums,
                        integer num_primary_key_atts,
                        text[] src_pk_att_vals_array,
                        text[] tgt_pk_att_vals_array) returns text

Description

dblink_build_sql_insert can be useful in doing selective replication of a local table to a remote database. It selects a row from the local table based on primary key, and then builds an SQL INSERT command that will duplicate that row, but with the primary key values replaced by the values in the last argument. (To make an exact copy of the row, just specify the same values for the last two arguments.)

Arguments

relname

Name of a local relation, for example foo or myschema.mytab. Include double quotes if the name is mixed-case or contains special characters, for example "FooBar"; without quotes, the string will be folded to lower case.

primary_key_attnums

Attribute numbers (1-based) of the primary key fields, for example 1 2.

num_primary_key_atts

The number of primary key fields.

src_pk_att_vals_array

Values of the primary key fields to be used to look up the local tuple. Each field is represented in text form. An error is thrown if there is no local row with these primary key values.

tgt_pk_att_vals_array

Values of the primary key fields to be placed in the resulting INSERT command. Each field is represented in text form.

Return Value

Returns the requested SQL statement as text.

Notes

As of PostgreSQL 9.0, the attribute numbers in primary_key_attnums are interpreted as logical column numbers, corresponding to the column's position in SELECT * FROM relname. Previous versions interpreted the numbers as physical column positions. There is a difference if any column(s) to the left of the indicated column have been dropped during the lifetime of the table.

Examples

SELECT dblink_build_sql_insert('foo', '1 2', 2, '{"1", "a"}', '{"1", "b''a"}');
             dblink_build_sql_insert
--------------------------------------------------
 INSERT INTO foo(f1,f2,f3) VALUES('1','b''a','1')
(1 row)

Prev Up Next
dblink_get_pkey Home dblink_build_sql_delete
Commercial use is possible only with written permission from the company LLC “Tantor Labs”
© LLC "Tantor Labs"
  • Technical Support Policy
  • Cookie Processing Policy
  • Website User Agreement
Products
  • Tantor DBMS
  • Tantor Platform
  • Documentation
Contacts
  • +7 495 369-48-16
  • info@tantorlabs.ru
16.8.1 - 8e8befb1 - 2025-04-10 15:44:23