PostgreSQL continued in sharding technology fdw based roots, the 9.6 Subject to
the conditions set, and JOIN support SORT pushed down to the data node
execution.
Here is a test
Create several shard databases
for subfix in 0 1 2 3
do
psql -c "create database db $ subfix"
done
Create a master d
Hi,
I have PostgreSQL v9.4.4 running in my environment. It has been up for over
2 years now. I noticed that suddenly the statistics have been reset and all
the stat tables/columns got restarted from.
This happened 2 weeks ago. I noticed only recently after I looked at the
plot over last week (whi
On 7/24/2016 4:45 PM, Peter Devoy wrote:
However, I would like to create a function which returns the resultset
of an INNER JOIN with table1 being polymorphic and table2 being a
result set of column types which do not change. Is this possible?
SQL tables are /not/ polymorphic.
--
john r pie
On Sunday, July 24, 2016, Peter Devoy wrote:
>
> However, I would like to create a function which returns the resultset
> of an INNER JOIN with table1 being polymorphic and table2 being a
> result set of column types which do not change. Is this possible?
>
Providing a concrete example might hel
Hi list
The example at the bottom of this
(http://stackoverflow.com/questions/11740256/11751557#11751557) answer
shows how the anyelement polymorphic type can be used to have a
function accept -- and return rows from -- an arbitrary table decided
by the user at runtime.
However, I would like to c
Melvin Davidson writes:
> I am not so sure another extension is needed. Would it not make more sense
> just to use the dblink extension?
That would be a quick-n-dirty fix, but it would give up all the guarantees
NOTIFY provides about messages being sent if and only if the sending
transaction comm
Mehran Ziadloo writes:
> What I meant was that the notifications are received by the client
> connectionsas if it was generated within their corresponding database (let's
> name thedatabase with a client connection listening to it; DB_C), then a
> notification generated by a NOTIFY command with
I understand that:
1) you like to use postgres as a "bus" to transfer messages between
connected clients;
2) only one database server is concerned (no redundancy at all);
3) it is the client code (perl, php ...) that send the notification (ie,
notifications are not sent by triggers for example)
M
On Sun, Jul 24, 2016 at 9:35 AM, Adrian Klaver
wrote:
> On 07/24/2016 03:31 AM, Mehran Ziadloo wrote:
>
>> I'm sorry, you are right. Let me rephrase that.
>>
>> What I meant was that the notifications are received by the client
>> connections
>> as if it was generated within their corresponding d
On 07/24/2016 03:31 AM, Mehran Ziadloo wrote:
I'm sorry, you are right. Let me rephrase that.
What I meant was that the notifications are received by the client
connections
as if it was generated within their corresponding database (let's name the
database with a client connection listening to i
I'm sorry, you are right. Let me rephrase that.
What I meant was that the notifications are received by the client
connectionsas if it was generated within their corresponding database (let's
name thedatabase with a client connection listening to it; DB_C), then a
notification generated by a NOT
On 7/23/2016 8:24 PM, Mehran Ziadloo wrote:
I'm looking for a way to send notifications from within one database to
another. As if pg_notify accepted a database name, or even to all of the
databases. So far I could not find a way to do so. Then someone told
me that I
need to implement this featu
12 matches
Mail list logo
