for this on
startup
+1
Andrew Chernow
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Anyway, from this POV all we really need to know is that the device
hosting this tablespace failed to mount when the machine was rebooted,
and then postgres restarted.
Good to know postgresql had nothing to do with the missing data. I
wasn't sure if it was user error, config problem or
at once
using a single method?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
is?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
; that can leak hints about the plaintext. Where is the randomly generated
IV stored for use during decryption?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
Andrew Dunstan wrote:
Andrew Chernow wrote:
Encrypting lots of small chunks of data with the same key is a very
dangerous thing to do and it's very tricky to get right.
Using an initialization vector (IV) is the way to go, recommend using
CBC or CFB mode. Although, an IV is never
were
attempting to detect behavior differences.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
to consider libpqtypes for contrib (which we don't have time for atm).
... or as a libpq sibling :)
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
if you'd like. Wouldn't be
until Monday or Tuesday. Any preference on windows version? Maybe
Windows 7? You want 64-bit?
Send a private email.
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
. You could track tuples
removed in an int[] or copy the result set into an application defined
array of C structures. I've always been under the impression that
PGresult objects are immutable once delivered to the application.
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com
PQmakeEmptyPGresult, PQsetResultAttrs and PQsetvalue to construct a
result that excludes the tuples you don't want followed by a
PQclear(initial_result)?
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
and PQsetvalue to construct a
result that excludes the tuples you don't want followed by a
PQclear(initial_result)?
Actually the best solution would be to call PQcopyResult with all
PG_COPYRES_XXX flags enabled except PG_COPYRES_TUPLES. Now call
PQsetvalue for each tuple you want to add.
--
Andrew
.
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
446 on fe-exec.c.
I never tested this case since libpqtypes never tried to call
PQsetvalue on a PGresult created by the standard libpq library.
The solution I see would be to zero the new table slots within
pqAddTuple. Any other ideas?
--
Andrew Chernow
eSilo, LLC
global backup
http
On 6/3/2011 4:06 PM, Andrew Chernow wrote:
On 6/3/2011 3:03 PM, Pavel Golub wrote:
Hello.
Reproduced under Windows XP SP3 using Visual C++ 2008 and Delphi. If
PQsetvalue is called with second parameter equals to PQntuples then
memory corruption appears. But it should grow internal tuples array
the tuple table; in which case new elements are
zero'd. OP attempted to append.
res = PQexec(returns 2 tuples);
PQsetvalue(res, PQntuples(res), ...);
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
as overwriting unless someone
speaks up. I fix the docs as well.
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
related to this change, it actually had to do with producing a result with
dead tuples that would cause PQgetvalue and others to crash. Thus, it seemed
better to only allow creating a result that is always *valid*.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via
the bug.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c
index 83c5ea3..9f013ed 100644
--- a/src/interfaces/libpq/fe-exec.c
+++ b/src/interfaces/libpq/fe-exec.c
@@ -424,28 +424,8 @@ PQsetvalue(PGresult
On 6/3/2011 10:26 PM, Andrew Chernow wrote:
I disagree -- I think the fix is a one-liner. line 446:
if (tup_num == res-ntups !res-tuples[tup_num])
should just become
if (tup_num == res-ntups)
also the memset of the tuple slots when the slot array is expanded can
be removed. (in addition
be it.
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
Have you looked into libpqtypes? It allows you to pack nested structures/arrays
and pass them as query/function parameters.
http://pgfoundry.org/projects/libpqtypes/
http://libpqtypes.esilo.com/ (docs)
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql
PQmakeEmptyPGresult, including libpqtypes.
Actually, libpqtypes calls PQcopyResult which calls PQmakeEmptyPGresult.
It might be better to say a server result vs. a client result.
Currently, PQsetvalue is broken when provided a server generated result.
--
Andrew Chernow
eSilo, LLC
global
the beginning
http://libpqtypes.esilo.com
http://pgfoundry.org/projects/libpqtypes/
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
A varargs version of PQexecParams() would be handy, though. Imagine being able
to do:
PQexecVParams(SELECT * FROM mytable WHERE foo = $1 AND bar = $2, foovar,
barvar);
instead of constructing an array for the variables.
http://libpqtypes.esilo.com/man3/PQexecf.html
--
Andrew Chernow
to make it feel more like C..
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
made a more formal set
of utility functions, typically called an API, in an attempt to match
the coding standards of the postgresql project.
There is no libpq param interface like results, so we added PGparam
stuff. This allows you to pack parameters (PQputf) and than execute it.
--
Andrew
/libpqtypes.
We do need some support in libpq for constructing and deconstructing
arrays (and probably for composites too, although that will be harder, I
suspect).
[sigh...]
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
the problem. Personally, PQexec is dead to me as well
as text results from a C/C++ app. I see no advantage over libpqtypes in
that context.
Unless I am missing your ultimate goal, you'd probably get what you want
by wrapping libpqtypes.
--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com
(conn,
select %int4 + %int4, 4, 4) is pretty far removed from the underlying
byte swapping, parallel array setup for PQexecParams and other
nastiness. But yes, the maintainer of the library must deal with
protocol changes and provide backward compatibility.
--
Andrew Chernow
eSilo, LLC
global
They are build farm boxes (which already build postgres) so my guess is they
wouldn't require much fiddling. I don't time to help with this, but am more
than willing to give you all the access you need to get it going.
I also have HP-UX 10.20 on a PA-RISC for the courageous.
--
Andrew Chernow
eSilo
.
// guc-file.c line 354
#define GUC_yywrap(n) 1
The macro is overriding the prototype declared at line 627, which has a void
argument list (assuming YY_SKIP_YYWRAP is !defined). Since all code references
to this do not provide an argument, I'd say the macro is incorrect.
--
Andrew Chernow
eSilo, LLC
301 - 332 of 332 matches
Mail list logo
