protocol would be implemented on HTTP/2.
- Similar to the above, but applied to the v4 TODO feature list.
- A section for connection poolers, as an auth, as these are very
important topics.
Hope this helps,
Álvaro
--
Alvaro Hernandez
---
OnGres
On 26/03/18 21:57, Damir Simunic wrote:
On 26 Mar 2018, at 15:42, Alvaro Hernandez <mailto:a...@ongres.com>> wrote:
On 26/03/18 13:11, Damir Simunic wrote:
On 26 Mar 2018, at 11:13, Vladimir Sitnikov
mailto:sitnikov.vladi...@gmail.com>>
wrote:
Damir> * What ar
I'm not a PG hacker, but all this sounds too complicated to me. I'd
keep the snapshot open that makes things very easy. If inside you want
to do parallel COPY, that's fine (if, as the other Álvaro said, it is
COPY the limiting factor).
Cheers,
Álvaro
--
Alvaro Hernandez
---
OnGres
a and then insert to the desired user requested size?
(or insert what should be the minimum, scale 1, measure, and extrapolate
what's missing). It doesn't sound too complicated to me, and targeting a
size is something that I believe it's quite good for user.
Álvaro
--
Alvaro Hernandez
---
OnGres
On 17/02/18 12:17, Tom Lane wrote:
Alvaro Hernandez writes:
On 17/02/18 11:26, Tom Lane wrote:
Fabien COELHO writes:
Here is a attempt at extending --scale so that it can be given a size.
I do not actually find this to be a good idea. It's going to be
platform-dependent, or not
ond suggestion seems more reasonable:
insert with scale 1, measure there (ok, you might need to crete indexes
only to later drop them), and if computed scale > 1 then insert whatever
is left to insert. Shouldn't be a big deal to me.
I like the feature :)
Álvaro
--
Alvaro Hernandez
---
OnGres
part of the conversation and/or this may be a
naïve question, but what about pg_stats? I guess data should be
encrypted there too, and I wonder how this would affect the query
planner and how it could decrypt this information. Also would a separate
key be used for the stats?
Thanks,
Álvaro
--
Alvaro Hernandez
---
OnGres
are
they trust-able? Do business want to rely on their encryption scheme,
key management, and how they respond from requests to hand off
encryption keys? I believe self-contained solutions are very worth, also
because of this.
Álvaro
--
Alvaro Hernandez
---
OnGres
at servers JDBC
would be able to connect to (using SCRAM + channel binding). Only those
with tls-server-end-point will be able to use CB with JDBC, and that is,
as of today, only OpenSSL 1.0.2 or higher, which is not available on
some older distributions.
Álvaro
--
Alvaro Hernandez
---
OnGres
ject.
- To add a proxy layer to any existing HA project is IMO a project on
its own. I don't even see this as a GSoC feasible project.
Cheers,
Álvaro
--
Alvaro Hernandez
---
OnGres
me addition, not to fire a new separate server and
exercise PITR, and then find the ways to move the old data around.
Regards,
Álvaro
--
Alvaro Hernandez
---
OnGres
and go for "AS OF TIMESTAMP", I'd recommend then, if possible, to:
- Make "TIMESTAMP" optional, i.e., "AS OF [TIMESTAMP] "
- Augment the syntax to support also a transaction id, similar to
Oracle's "AS OF SCN ": "AS OF TRANSACTION ".
Merry Christmas,
Álvaro
--
Alvaro Hernandez
---
OnGres
12 matches
Mail list logo