Is there a web page describing how to set up a PG FDW to talk to DB2 LUW ver
10.5 ?
Thanks.
> You mean Oracle 11g.
No 12c. Some of it may have started in 11g itself, but only in 12c they really
mastered it. I saw it as a developer, not as a DBA. I was never an oracle DBA.
> For example, the planner may be able to
> more easily recognise a statement and reuse an existing plan rather than
> re-planning the query.
This is a double edged sword. Reuse an existing plan can be bad in those
cases where the data distribution is not suitable for the current plan. This has
b
> On Mar 1, 2018, at 12:47 , Daevor The Devoted wrote:
>
>
> I was always of the opinion that a mandatory surrogate key (as you describe)
> is good practice.
> Sure there may be a unique key according to business logic (which may be
> consist of those
> "ungainly" multiple columns), but gue
>Adding a surrogate key to such a table just adds overhead, although that could
>be useful
>in case specific rows need updating or deleting without also modifying the
>other rows with
>that same data - normally, only insertions and selections happen on such
>tables though,
>and updates or de
>
> I'm not sure about the terminology here, though, because the Transaction
> Tutorial
> (https://www.postgresql.org/docs/9.6/static/tutorial-transactions.html)
> speaks of "aborted" transactions, while you use the term "failed" here.
Purely from a user point of view, shouldn't "aborted" mean a
>We are looking for multi tenancy but at scale. That's why the sharding and
>partitioning. It depends how you look at the distributed part.
Citusdb.
> On Jan 29, 2018, at 09:34 , Matej wrote:
>
> Hi Everyone.
>
> We are looking at a rather large fin-tech installation. But as scalability
> requirements are high we look at sharding of-course.
>
> I have looked at many sources for Postgresql sharding, but we are a little
> confused as to
correct.
-Original Message-
From: Azimuddin Mohammed
To: Rakesh Kumar
Cc: pgsql-admin ; pgsql-general
Sent: Thu, Jan 25, 2018 8:06 pm
Subject: Re: Sync replication
So untill my slave comes up master does not commit any transaction which means
technically my db is non operative
>I have a question regarding synchronus replication.
>If i have a master and standby server will sync replication setup..when my
>slave dies and master is still active. Will the transaction completes, or
>>master will wait for slave to commit the transaction and then commits its. ?
Master
Is there a way to grant PG permissions to unix/LDAP groups instead of
individuals.
Seems like PG lacks it, unless there is an extension I am not aware of.
why are you not using CACHE clause which is precisely for the purpose :
cache
The optional clause CACHE cache specifies how many sequence numbers are to be
preallocated and stored in memory for faster access. The minimum value is 1
(only one value can be generated at a time, i.e., no cache), and
> And what is the difference between index scan and index only scan.
Index scan: Index lookup for key access plus read from data blocks to satisfy
the query.
Index only scan: Index lookup for key access plus read from index pages itself
to satisfy query. In other words, entire query can
be
>I'm probably missing something, but can anyone see a reason why adding an ADD
>OR >ALTER COLUMN syntax to the ALTER TABLE command isn't either a) achievable
>or b) >desirable?
>It seems to me to be eminently useful and not overly difficult, while
>potentially >saving a significant amount of eff
> > I also would like to believe that the hit is small, but when PG
> > official document writes "noticeable performance penalty", it becomes
> > difficult to convince management that the hit is small :-)
>
> Why believe, when you can measure?
yup doing that. But I still feel that PG documentat
Hello Mr. Pedantic,
> noticeable != huge.
and noticeable != small/negligible either, at least from English point of view.
> That said, imv anyway, the performance hit is small and having checksums
> is well worth it.
I also would like to believe that the hit is small, but when PG official
document writes "noticeable performance penalty", it becomes difficult to
convince management that the hit is small :-)
--data-checksums
Use checksums on data pages to help detect corruption by the I/O system that
would otherwise be silent. Enabling checksums may incur a noticeable
performance penalty. This option can only be set during initialization, and
cannot be changed later. If set, checksums are calculated
You should have read carefully what I wrote. 1000 is not an upper limit.
1000 partition is the number after which performance starts dropping .
There is a blog in www.timescale.com which also highlights the same.
Sent: Monday, January 08, 2018 at 6:20 PM
From: "Kumar, Virendra"
To: "pgsql
Shouldn't isolation level also matter ? What is the isolation level you are
using ?
Well I do recollect the option in the old mailing list to not email any postings. IIRC, there were following options:
1- Email every messgages
2- Daily digest of messages
3- No email of any message.
Option (3) can be used for only posting. I did that for some time.
> The tool Im using is "sqlplus". By default you are always in a transaction
> and
> auto-commit only occur on exit.
Its been a while since I worked with oracle. I remember I use to add the
following two lines at the top:
SET AUTOCOMMIT OFF
whenever SQLERROR EXIT ROLLBACK
IIRC, adding the abo
Could it be that the tool you are using in Oracle is doing commit while exiting
out due to Deadlock, because there is no explicit rollback.
I want to confirm my understanding. When a stored procedure is called the
first time the code's compiled version is cached and used next time it is
executed. However it is cached once for every session and not globally for all
sessions. In other words, if we have a large number of concurrent s
Has AWS Aurora started supporting PG 10. Their website still talks about 9.6.
Thanks
> There are multiple solutions to doing incremental backups with
> PostgreSQL, so I'm not sure why you're saying that they don't exist,
> because that's really not accurate.
PG's incremental backup is essentially WAL logs applied to a point in time. I
am talking about true incremental backup wh
I think with 100TB the biggest challenge will be taking backups. PG has no real
incremental backups offered in Oracle or SQLServer.
> Just what I was thinking. Are you looking in the correct database?
All: He has already replied to me earlier that he had indeed dropped the
schema before creating it.
>What is difference between CLOCK_TIMESTAMP() and CURRENT_TIMESTAMP?
CURRENT_TIMESTAMP stays the same within the transaction. It is very useful when
you
are you inserting to multiple tables and want to use the timestamp columns to
chain the rows
together.
CLOCK_TIMESTAMP is the true timestam
Sorry, outlook is not showing all mails. Trying this now.
why is that I did not receive the first 4 emails on this topic? I see that
only the old email address "pgsql-gene...@postgresql.org" is mentioned. Could
that be the reason ?
ps: I am adding the new lists address.
On 2017-11-21 19:02:01 -0500, Tom Lane wrote:
> and...@anarazel.de (An
31 matches
Mail list logo