fix test and add readme

Author: maryliag

plugins/node/opentelemetry-instrumentation-pg/README.md

@@ -51,6 +51,48 @@ PostgreSQL instrumentation has few options available to choose from. You can set
 | `requireParentSpan` | `boolean` | If true, requires a parent span to create new spans (default false) |
 | `addSqlCommenterCommentToQueries` | `boolean` | If true, adds [sqlcommenter](https://github.com/open-telemetry/opentelemetry-sqlcommenter) specification compliant comment to queries with tracing context (default false). _NOTE: A comment will not be added to queries that already contain `--` or `/* ... */` in them, even if these are not actually part of comments_ |
 
+## Semantic Conventions
+
+Prior to version `0.55.0`, this instrumentation created spans and metrics targeting an experimental semantic convention Version 1.27.0.
+
+Database semantic conventions (semconv) were stabilized in v1.34.0, and a [migration process](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/db-migration.md) was defined.
+`opentelemetry-instrumentation-pg` versions 0.55.0 and later include support for migrating to stable Database semantic conventions, as described below.
+The intent is to provide an approximate 6 month time window for users of this instrumentation to migrate to the new Database semconv, after which a new minor version will use the *new* semconv by default and drop support for the old semconv.
+
+To select which semconv version(s) is emitted from this instrumentation, use the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable.
+
+- `database`: emit the new (stable) v1.34.0+ semantics
+- `database/dup`: emit **both** the old v1.27.0 and the new (stable) v1.34.0+ semantics
+- By default, if `OTEL_SEMCONV_STABILITY_OPT_IN` includes neither of the above tokens, the old v1.27.0 semconv is used.
+
+### Attributes collected
+
+| v1.27.0 semconv         | v1.34.0 semconv                                 | Short Description                                                                          |
+| ----------------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------ |
+| `db.connection_string`  | Removed                                         | String used to connect to the database                                                     |
+| `db.user`               | Removed                                         | User used to connect to the database                                                       |
+| `db.name`               | Removed, integrated into the new `db.namespace` | The name of the database.                                                                  |
+| (not included)          | `db.namespace`                                 | The name of the database, fully qualified within the server address and port.              |
+| `db.statement`          | `db.query.text`                                 | The database query being executed.                                                         | 
+| `db.system`             | `db.system.name`                                | The database management system (DBMS) product as identified by the client instrumentation. |
+| `net.peer.port`         | `network.peer.port`                             | Peer port number of the network connection.                                                |
+| `net.peer.name`         | `network.peer.address`                          | Peer address of the database node where the operation was performed.                       |
+
+Metrics Exported:
+
+- [`db.client.operation.duration`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-metrics.md#metric-dbclientoperationduration)
+
+### Upgrading Semantic Conventions
+
+When upgrading to the new semantic conventions, it is recommended to do so in the following order:
+
+1. Upgrade `@opentelemetry/opentelemetry-instrumentation-pg` to the latest version
+2. Set `OTEL_SEMCONV_STABILITY_OPT_IN=database/dup` to emit both old and new semantic conventions
+3. Modify alerts, dashboards, metrics, and other processes to expect the new semantic conventions
+4. Set `OTEL_SEMCONV_STABILITY_OPT_IN=database` to emit only the new semantic conventions
+
+This will cause both the old and new semantic conventions to be emitted during the transition period.
+
 ## Useful links
 
 - For more information on OpenTelemetry, visit: <https://opentelemetry.io/>

plugins/node/opentelemetry-instrumentation-pg/src/semconv.ts

@@ -109,43 +109,43 @@ export const ATTR_DB_SYSTEM = 'db.system';
  * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
  *
  */
-export const DB_SYSTEM_VALUE_POSTGRESQL = "postgresql";
+export const DB_SYSTEM_VALUE_POSTGRESQL = 'postgresql';
 
 /**
  * If no [tech-specific attribute](#call-level-attributes-for-specific-technologies) is defined, this attribute is used to report the name of the database being accessed. For commands that switch the database, this should be set to the target database (even if the command fails).
  *
  * Note: In some SQL databases, the database name to be used is called "schema name".
  *
  */
-export const ATTR_DB_NAME = "db.name";
+export const ATTR_DB_NAME = 'db.name';
 
 /**
  * The connection string used to connect to the database. It is recommended to remove embedded credentials.
  *
  */
-export const ATTR_DB_CONNECTION_STRING = "db.connection_string";
+export const ATTR_DB_CONNECTION_STRING = 'db.connection_string';
 
 /**
  * Username for accessing the database.
  *
  */
-export const ATTR_DB_USER = "db.user";
+export const ATTR_DB_USER = 'db.user';
 
 /**
  * Remote port number.
  *
  */
-export const ATTR_NET_PEER_PORT = "net.peer.port";
+export const ATTR_NET_PEER_PORT = 'net.peer.port';
 /**
  * Remote hostname or similar.
  *
  */
-export const ATTR_NET_PEER_NAME = "net.peer.name";
+export const ATTR_NET_PEER_NAME = 'net.peer.name';
 
 /**
  * The database statement being executed.
  *
  * Note: The value may be sanitized to exclude sensitive information.
  *
  */
-export const ATTR_DB_STATEMENT = "db.statement";
+export const ATTR_DB_STATEMENT = 'db.statement';