Question 1

How do I set up a reactive PostgreSQL query in Meteor with numtel:pg?

Accepted Answer

On the server, create a LivePg instance and use its select() method to publish a query, like in the README's players example. On the client, instantiate PgSubscription with the publication name to subscribe without extra Meteor.subscribe calls.

Question 2

What are the differences between numtel:pg and Meteor's native MongoDB reactivity?

Accepted Answer

numtel:pg extends Meteor's reactivity to PostgreSQL, allowing SQL-based real-time updates, while MongoDB has built-in support. However, numtel:pg requires manual trigger management and is limited to SELECT queries, unlike MongoDB's full CRUD reactivity.

Question 3

Can I perform INSERT or UPDATE operations reactively with numtel:pg?

Accepted Answer

No, reactive updates are only for SELECT queries. For other operations, use the exposed pg object from node-postgres, but changes won't automatically push to clients unless tied to a reactive query.

Question 4

How do I handle database cleanup when restarting the Meteor server?

Accepted Answer

Add event handlers for SIGTERM and SIGINT to call the cleanup() method on LivePg instances, as shown in the README. This removes old triggers and functions to prevent accumulation during hot code pushes.

Question 5

What PostgreSQL versions work with numtel:pg?

Accepted Answer

It requires PostgreSQL version 9.3 or higher, as specified in the README, due to features needed by the underlying pg-live-select module for reactive capabilities.

Question 6

Is there a way to test numtel:pg without a separate PostgreSQL installation?

Accepted Answer

Yes, use the numtel:pg-server Meteor package to bundle PostgreSQL directly, and configure the test settings in test/settings/local.json, as mentioned in the README's test section for running benchmarks.

numtel:pg

What is numtel:pg?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions