Le 09/06/2015 02:29, Craig Ringer a écrit :
Questions:
---
-Is it a known bug? If yes should I report it (and where)?
Please open a report on github for this -
https://github.com/2ndQuadrant/bdr/issues
=> https://github.com/2ndQuadrant/bdr/issues/87
-How to rec
On Mon, Jun 8, 2015 at 10:15 AM, Dave Johansen
wrote:
> I'm using Postgres 8.4 on RHEL 6 and I need to support inserting data into
> a table from multiple processes with there occasionally being duplicates
> from the different processes. Here's a simple example table:
> CREATE TABLE test (tutc TI
Hi Ian,
Thank you so much for your help.
After changing the hot_standby = on to hot_standby = off, everything is working
fine. We have copied all parameters from current production environment.
Thanks
ravi
-Original Message-
From: Ian Barwick [mailto:i...@2ndquadrant.com]
Sent: Mond
Hi All,
I have one requirement in my project and don't know how to achieve.
My project is receiving the log information from PC in the network, and that
information is stored in the below table.
CREATE TABLE "PCLogTable"
(
"LOG_ID" serial NOT NULL,
"LOG_USER_ID" integer DEFAULT 0,
"LOG_TY
On Tue, Jun 9, 2015 at 4:48 AM, Yelai, Ramkumar IN BLR STS <
ramkumar.ye...@siemens.com> wrote:
> Now, the requirement is if user provides filter information based on
> every column from the web UI, this filter will let the user construct the
> “where clause” and provide to postgresql.
> In a mon
There has been some confusion by old and new community members about the
purpose of the core team, and this lack of understanding has caused some
avoidable problems. Therefore, the core team has written a core charter
and published it on our website:
http://www.postgresql.org/developer/co
SQL Server has a feature called Indexed Views that are similiar to
materialized views.
Basically, the Indexed View supports COUNT/SUM aggregate queries. You
create a unique index on the Indexed View and SQL Server automatically
keeps the COUNT/SUM upto date.
Example:
CREATE VIEW ForumTopicCounts
Though I'm sure you've already looked into it, for your specific issue of
getting row counts:
- In PostgreSQL 9.2 and above this operation can be made much faster with
index-only scans so ensure you are on a recent version and do your count on
a column of a candidate key with an index (for example,