Postgres to Clickhouse Connection issue about peerdb

[serprex]

Thanks, I'll look into this tomorrow

[saisrirampur]

@Amogh-Bharadwaj @serprex can we take a look at this. Thanks for reporting @jbeck018

[serprex]

@jbeck018 can you share a schema that's running into this issue?

[jbeck018]

@serprex I have three seperate ones (just a small snapshot of our entire db). Here is the largest of the three that was created by PeerDB in Clickhouse itself:

) show create table account

SHOW CREATE TABLE account

Query id: 6acc46f3-4d49-49ce-8c90-83bfba916359

┌─statement──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ CREATE TABLE default.account
(
    `id` UUID,
    `created_at` DateTime64(6),
    `updated_at` DateTime64(6),
    `organizationID` UUID,
    `displayName` String,
    `objectSource` String,
    `accountType` String,
    `searchName` String,
    `vip` Bool,
    `primaryContactID` UUID,
    `primaryDecisionMakerID` UUID,
    `niceToHaveNeedsCount` Int64,
    `needsCount` Int64,
    `urgentNeedsCount` Int64,
    `currentRevenue` Decimal(30, 2),
    `closedLostRevenue` Decimal(30, 2),
    `openOpportunityRevenue` Decimal(30, 2),
    `lifetimeValue` Decimal(30, 2),
    `vipNeedsCount` Int64,
    `needToHaveNeedsCount` Int64,
    `opportunitiesCount` Int64,
    `notUrgentNeedsCount` Int64,
    `accountPlan` String,
    `upcomingRenewalDate` DateTime64(6),
    `transactionRevenue` Decimal(30, 2),
    `transactionCount` Decimal(30, 2),
    `adminID` UUID,
    `openNeedsCount` Int64,
    `openUrgentNeedsCount` Int64,
    `totalCurrentRevenue` Decimal(30, 2),
    `totalClosedLostRevenue` Decimal(30, 2),
    `totalPotentialRevenue` Decimal(30, 2),
    `totalLifetimeValue` Decimal(30, 2),
    `openCurrentRevenue` Decimal(30, 2),
    `openClosedLostRevenue` Decimal(30, 2),
    `openPotentialRevenue` Decimal(30, 2),
    `openLifetimeValue` Decimal(30, 2),
    `resolvedCurrentRevenue` Decimal(30, 2),
    `resolvedClosedLostRevenue` Decimal(30, 2),
    `resolvedPotentialRevenue` Decimal(30, 2),
    `resolvedLifetimeValue` Decimal(30, 2),
    `openNeedToHaveNeedsCount` Int64,
    `openNiceToHaveNeedsCount` Int64,
    `openNotUrgentNeedsCount` Int64,
    `changeMakerType` String,
    `changeMakerID` String,
    `atRisk` Bool,
    `lifeCycleStageID` UUID,
    `userCount` Int32,
    `cachedAt` DateTime64(6),
    `accountGroupID` UUID,
    `CSATScore` Decimal(76, 38),
    `NPSScore` Decimal(76, 38),
    `excludedFromAutomations` Bool,
    `parentId` UUID,
    `_peerdb_synced_at` DateTime64(9) DEFAULT now(),
    `_peerdb_is_deleted` Int8,
    `_peerdb_version` Int64
)
ENGINE = ReplacingMergeTree(_peerdb_version)
PRIMARY KEY id
ORDER BY id
SETTINGS index_granularity = 8192 │
└──────────────────────────────────────────────────────────────────────

[serprex]

@jbeck018 & the postgres schema?

[jbeck018]

Was just grabbing it, psql tool wasn't allowing me to printout all the actual columns for table.
I ended up having to print table information and exporting via CSV. let me know if you need more information than the following:

[serprex]

@jbeck018 Amogh was not able to reproduce, but created #1442 as a theory for what could be the issue here. Can you test that PR?