Getting an error: `prepared statement "table:undefined" already exists`
```ts
const defaultTableName = "table";

const pool = new Pool({
    connectionString: config.db.URL,
});

const dayLimiterOptions: IRateLimiterPostgresOptions = {
    storeClient: pool,
    tableName: defaultTableName,
    schemaName,
    keyPrefix: "day",
    duration: 60 * 60 * 24,
    points: 2000 * rateLimitPercentage,
};

export function initializeRateLimiterPostgres(
    options: IRateLimiterPostgresOptions,
): Promise<RateLimiterPostgres> {
    return new Promise((resolve, reject) => {
        let rateLimiter: RateLimiterPostgres;
        const ready = (err: unknown) => {
            if (err) {
                reject(err);
            } else {
                resolve(rateLimiter);
            }
        };

        rateLimiter = new RateLimiterPostgres(options, ready);
    });
}

const defaultDayLimiter =
        await initializeRateLimiterPostgres(dayLimiterOptions);
        
const defaultDayLimiterQueue = new RateLimiterQueue(defaultDayLimiter);
```

Above are the options I'm using to initialize the rate limiter, I have 6 instances of `RateLimiterPostgres` using the same pool but with different points/tables used.  
I also have the same configuration in 2 separate services.

Intermittenly when initializing one of these `RateLimiterPostgres` instances I receive the error `prepared statement "table:undefined" already exists`

Intermittenly when consuming credits via `RateLimiterQueue`:  
`await defaultDayLimiter.removeTokens(1, url)`
I receive the error `prepared statement "table:rlflx-upsert" already exists`

Initially I've used the code:
```ts
await Promise.all([
    await defaultDayLimiter.removeTokens(1, url);
    await defaultHourLimiter.removeTokens(1, url);
    await defaultMinutesLimiter.removeTokens(1, url);
]);
```
Also tried to run it in series:
```ts
await defaultDayLimiter.removeTokens(1, url);
await defaultHourLimiter.removeTokens(1, url);
await defaultMinutesLimiter.removeTokens(1, url);
```

Both produced the same error, doesn't seem to be sticking to one service. Seems to be happening intermittently and across both services