I don't know if this is relevant, but we use the default streaming
replication and were not always keeping up. Now we WAL log ship to S3
bucket... seems to work pretty well... cheers Ben
On 5 December 2017 at 17:12, Job wrote:
> Hi guys,
>
> we have some postgreswl 9.6.1 servers in two different
On Tue, Dec 5, 2017 at 5:43 PM, Jeff Janes wrote:
> On Mon, Dec 4, 2017 at 5:52 PM, John R Pierce wrote:
>> On 12/4/2017 2:21 PM, chris kim wrote:
>>> How would I investigate if my database is nearing a transaction wrap
>>> around.
>>
>> it would be screaming bloody murder in the log, for one.
>>
Partition pruning doen't work in this case
as described at
http://www.postgresql-archive.org/Partition-pruning-for-Star-Schema-td5995163.html#a5995168
Partition wise join works for ONLY ONE dim table (that is better than
nothing).
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-gener
You might as well try Slony.
Best Regards,
Nawaz Ahmed
-Original Message-
From: Job [mailto:j...@colliniconsulting.it]
Sent: Tuesday, 5 December 2017 8:12 PM
To: pgsql-gene...@postgresql.org
Subject: Replica on low-bandwitdh network
Hi guys,
we have some postgreswl 9.6.1 servers in
Carl Karsten wrote:
> On Tue, Dec 5, 2017 at 4:15 PM, Alvaro Herrera
> wrote:
> > A backup generated by pg_dump never includes writes that are in flight
> > while the backup is being taken. That would make the backup absolutely
> > worthless!
>
> Hmm, i kinda glossed over my point:
> if you com
On 12/5/2017 2:09 PM, Martin Mueller wrote:
Time is not really a problem for me, if we talk about hours rather
than days. On a roughly comparable machine I’ve made backups of
databases less than 10 GB, and it was a matter of minutes. But I know
that there are scale problems. Sometimes program
On Tue, Dec 5, 2017 at 4:15 PM, Alvaro Herrera
wrote:
> Carl Karsten wrote:
> > Nothing wrong with lots of tables and data.
> >
> > Don't impose any constraints on your problem you don't need to.
> >
> > Like what are you backing up to?$400 for a 1T ssd or $80 fo a 2T usb3
> > spinny disk.
>
On Tue, Dec 5, 2017 at 3:09 PM, Martin Mueller <
martinmuel...@northwestern.edu> wrote:
> Time is not really a problem for me, if we talk about hours rather than
> days. On a roughly comparable machine I’ve made backups of databases less
> than 10 GB, and it was a matter of minutes. But I know t
Carl Karsten wrote:
> Nothing wrong with lots of tables and data.
>
> Don't impose any constraints on your problem you don't need to.
>
> Like what are you backing up to?$400 for a 1T ssd or $80 fo a 2T usb3
> spinny disk.
>
> If you are backing up while the db is being updated, you need to
Time is not really a problem for me, if we talk about hours rather than days.
On a roughly comparable machine I’ve made backups of databases less than 10 GB,
and it was a matter of minutes. But I know that there are scale problems.
Sometimes programs just hang if the data are beyond some size.
Nothing wrong with lots of tables and data.
Don't impose any constraints on your problem you don't need to.
Like what are you backing up to?$400 for a 1T ssd or $80 fo a 2T usb3
spinny disk.
If you are backing up while the db is being updated, you need to make sure
updates are queued until t
On Tue, Dec 5, 2017 at 2:52 PM, Martin Mueller <
martinmuel...@northwestern.edu> wrote:
> Are there rules for thumb for deciding when you can dump a whole database
> and when you’d be better off dumping groups of tables? I have a database
> that has around 100 tables, some of them quite large, and
Are there rules for thumb for deciding when you can dump a whole database and
when you’d be better off dumping groups of tables? I have a database that has
around 100 tables, some of them quite large, and right now the data directory
is well over 100GB. My hunch is that I should divide and conqu
On 12/5/2017 1:11 PM, Karsten Hilbert wrote:
On Tue, Dec 05, 2017 at 09:59:22PM +0100, Riccardo Bassani wrote:
https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking
There's already at least 4 mechanismus that come to mind
which can do things like that:
I will have a look, thank you for the tips!
2017-12-05 22:11 GMT+01:00 Karsten Hilbert :
> On Tue, Dec 05, 2017 at 09:59:22PM +0100, Riccardo Bassani wrote:
>
>> https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking
>
> There's already at least 4 mechanismus that
Sorry, I don't develop in C.
I could always learn how to develop in C, and how it works a DBMS, but
it will take some time :)
Anyway it's interisting to see some some people interested in that feature, too.
2017-12-05 22:03 GMT+01:00 Alvaro Herrera :
> Riccardo Bassani wrote:
>> As SQL Server 201
On Tue, Dec 05, 2017 at 09:59:22PM +0100, Riccardo Bassani wrote:
> https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking
There's already at least 4 mechanismus that come to mind
which can do things like that:
on SELECT RULEs
VIEWs
colu
Riccardo Bassani wrote:
> As SQL Server 2016 (
> https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking
> ) , or Oracle does: it could be a neat feature having Dynamic Data
> Masking, even if it has some limitations, it could help in the
> application development, i
As SQL Server 2016 (
https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking
) , or Oracle does: it could be a neat feature having Dynamic Data
Masking, even if it has some limitations, it could help in the
application development, imho.
I know it's possible to put
From: Eugene Poole [mailto:etpool...@comcast.net]
Sent: Tuesday, December 05, 2017 12:59 PM
To: pgsql-gene...@postgresql.org
Subject: Migrating From CentOS-6 Oracle 11g R2 To CentOS-7 PostgreSQL ??
I've asked most of my OS based questions on another mail list, but I think this
is more specific:
I've asked most of my OS based questions on another mail list, but I
think this is more specific:
On a physical machine I'm running CentOS-6 64-bit with Oracle 11gR2 and
I want to migrate to another physical machine running CentOS-7 64-bit
with PostgreSQL ??
1. What version of PostgreSQL
On Tue, Dec 5, 2017 at 1:12 AM, Job wrote:
> we have some postgreswl 9.6.1 servers in two different continent.
> Latency is from 180 to 250 ms between the two sites.
>
> Actually we use Rubyrep for off-site replication, since servers are
> completely independent in case of connectivity loss.
>
>
On Tue, Dec 5, 2017 at 4:09 AM, Brahmam Eswar wrote:
> Thanks David for your quick response.
>
> I'm using below query to pull the schema information ,but the count of
> rows in table is giving wrong ,i can see the count of records using select
> count(*) from . How do we get an exact number of
Hi guys,
we have some postgreswl 9.6.1 servers in two different continent.
Latency is from 180 to 250 ms between the two sites.
Actually we use Rubyrep for off-site replication, since servers are completely
independent in case of connectivity loss.
We are experiencing some problems with lock ta
Thanks David for your quick response.
I'm using below query to pull the schema information ,but the count of rows
in table is giving wrong ,i can see the count of records using select
count(*) from . How do we get an exact number of rows in table.
SELECT C.relname AS Table_Name,
C.relnatts AS
25 matches
Mail list logo
