Jeff,
Great info! Your example on Mr. Mrs. Miss, etc. is there a good rule of
thumb that if the data is under "x"KB an index is overhead not help? I am
not worried about space, more interested in performance.
There are many possible problems, could you share your command line?
For example. Dump on SAME drive as the DB files, can produce disk
contention. Dump across the network, can have packet collision of network
latency. I dump 20gb test server in a matter of a couple minutes here. But,
I run
Ok.
On Wed, Jun 13, 2018 at 12:00 PM Caglar Aksu wrote:
> Dont mail me plase unsubscribe
>
Sorry...
> 1) CoC might result in developers leaving projects
I know this on going regurgitation is going to cause my team to leave
the project, right around 100 posts on this off topic topic it was bad
enough when the original idea came up (2 years ago I think). It used to be
- but the key is public (dumb)
https://www.postgresql.org/message-id/ca%2bcsw_tb3bk5i7if6inzfc3yyf%2b9hevnty51qfboeuk7ue_v%...@mail.gmail.com
Just because you do not see the reason for it, does not make the reason a
bad idea.
On Fri, Apr 20, 2018 at 8:19 PM Ozz Nixon <ozzni...@gmail.com> wrote:
Well, actually since 2003, this has been a standard requirement from the
Credit Card industry. And it does make sense in the field of "while at
rest" the data still cannot be accessed.
Requirement 1. No NPI data should be displayed without controls - e.g.
reports, PDF, etc.
Requirement 2. Same
