Alvaro Herrera wrote:
Andrew Chernow escribió:
Attached is the latest patch. It has addressed the requested changes
found here:
http://archives.postgresql.org/pgsql-patches/2008-05/msg00389.php
Its a tarball because there are two new files, libpq-events.c and
libpq-events.h. The patch
*/
if((options PG_COPYRES_ATTRS)
!PQsetResultAttrs(dest, src-numAttributes, src-attDescs))
{
PQclear(dest);
return NULL;
}
So, there is some nice code reuse which indicates to me the code is
segmented well (copyres setattrs).
--
Andrew Chernow
eSilo, LLC
every bit counts
http
Alvaro Herrera wrote:
Andrew Chernow escribió:
Alvaro Herrera wrote:
(I also removed PQresultAlloc.)
Nooo ... removing PQresultAlloc breaks libpqtypes! It also removes
some of the use cases provided by PQsetvalue, which allows one to add to
a result (in our case from scratch).
I
the instanceData functions within its eventproc, but this
is not a requirement.
All those who oppose any of the above, speak now or forever hold your
peace. An updated patch with full sgml documentation is coming.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql
Andrew Chernow wrote:
I think it got confused with the instanceData feature, which has nothing
to do with the event system and requires public functions. libpqtypes
happens to use the instanceData functions within its eventproc, but this
is not a requirement.
I forgot to mention
that may be related.
P GNUmakefile.in
P configure
P configure.in
P src/Makefile.global.in
P src/backend/common.mk
--
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
Alvaro Herrera wrote:
Actually a minor gripe ... should PQsetvalue be PQsetValue? :-)
We were mimicing PQgetvalue, which uses a lowercase 'v'. Is there a
preference, none on this end.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing
- thin wrapper around the internal pqResultAlloc. Uses the
result's block allocater, which allows PQclear to properly free all memory
assocaited with a PGresult.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
.
--
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
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
Missed that one. Good catch :) Update attached.
Looking at this now. Question: why does PQgetResult invoke the
RESULTCREATE event only for non-error results?
It didn't seem useful to have the eventproc implementation allocate its
).
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
Index: src/interfaces/libpq/fe-exec.c
===
RCS file: /projects/cvsroot/pgsql/src/interfaces/libpq/fe-exec.c,v
retrieving revision 1.198
diff -C6 -r1.198 fe-exec.c
*** src
Andrew Chernow wrote:
Now, it's questionable how tense we need to be about that as long as
event proc failure aborts calling of later event procs. That means
that procs have to be robust against getting DESTROY with no CREATE
calls in any case. Should we try to make that less uncertain
' member, I should
initialize it to FALSE. I did not do this in the last patch ...
register function.
--
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 Chernow wrote:
New patch following our discussion with updated docs.
few logical errors). I don't think it makes sense to do it
otherwise, it would be like calling free after a malloc failure.
I can live with that definition, but please document it.
To build on this analogy
Are there any plans to commit these libpq-events changes this fest?
http://archives.postgresql.org/pgsql-hackers/2008-09/msg01109.php
I wanted to release an updated libpqtypes but am waiting on the above
patch. If not, I'll release it now.
--
Andrew Chernow
eSilo, LLC
every bit counts
http
event
PQgetResult now calls PQfireResultCreateEvents.
BTW, the event system might be an alternative solution for PGNoticeHooks
(PGEVT_NOTICE).
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
Index: doc/src/sgml/libpq.sgml
also want to give the eventproc a chance to issue a
PQinstanceData call, so it can copy stuff to the created result.
--
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
history, it has
survived its 'replacements' over and over again. The most popular
kernels, shells and applications are all still written in C (new and
old). Where are the warning signs that it is dwindling?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql
://pgfoundry.org/frs/?group_id=1000370
NOTE: requires using cvs head because libpqtypes needs the new
libpq-events feature.
--
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
bug
- bad disk sector
- power crash
- weird martian-like raid rebuilds
Although, this idea won't prevent anything. Everything would still sinisterly
fail on you. The difference is, no more silence.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers
likely
to have collisons than zero (or any other arbitrary value)?
Would it not be better to add a boolean bit or byte to inidcate the crc
state?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
timestamp types. Therefore, any limitations in regards to 64-bit time_t
values on 32-bit platforms don't apply; other than the limitation Tom
spoke of ... no 64-bit int.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
.
--
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
Magnus Hagander wrote:
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
Tom Lane wrote:
Does fork/exec preserve lock ownership on Windows?
Not to my knowledge. On windows, there is only CreateProcess
(http://msdn.microsoft.com/en-us/library/ms682425.aspx). That doesn't
resemble
that?)
* Set it running
Not sure, but the SECURITY_ATTRIBUTES argument to CreateFile has a
bInheritHandle member that specifies whether a child process can inherit
the fiel HANDLE. I'm not sure if that would include locks on the file
HANDLE.
--
Andrew Chernow
eSilo, LLC
every bit
Andrew Chernow wrote:
Tom Lane wrote:
Hmm. Now that you mention it, didn't we solve a similar problem by
exploiting the behavior where CreateProcess creates a process but
doesn't start it running? I'm envisioning
* Create child process in suspended state
* Assign it ownership
.
The docs state the system closes the handle (mutex) when the process
terminates and makes no mention of this being a lingering action like
LockFileEx. It sounds like the mutex is closed ASAP when the process
terminates, just like file handles.
--
Andrew Chernow
eSilo, LLC
every bit counts
);
}
CloseHandle(h);
return 0;
}
--
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
Andrew Dunstan wrote:
Andrew Chernow wrote:
Andrew Dunstan wrote:
Has anyone considered not using a file lock on windows? CreateMutex
might do the trick if provided a mutex name, making it global rather
than process bound. OpenMutex can be used to test if the mutex
exists
David E. Wheeler wrote:
On Oct 21, 2008, at 12:08, Simon Riggs wrote:
If we got rid of zero dimension arrays, how would I declare a new empty
array in a PL/pgSQL function?
Why would you want to do that? Is there a use case for that?
--
Andrew Chernow
eSilo, LLC
every bit counts
http
.
--
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
the lookup key. For this case, a public function
that returns the address of the private static not dllexport
PGEventProc would be required.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
Just noticed that the last libpqtypes release was broken on windows when
dynamically linking. The problem is that windows has two addresses for
functions, the import library uses a stub ordinal address while the
DLL itself is using
Andrew Chernow wrote:
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
Just noticed that the last libpqtypes release was broken on windows
when dynamically linking. The problem is that windows has two
addresses for functions, the import library uses a stub ordinal
address while
;-)
(threading issues here)
There is no unregister, so the idea won't lock/unlock in high traffic
routines.
On the whole I vote for #4 out of these.
Okay.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
of these.
I attached a patch for the docs. Its documented as a NOTE to the
PGEventProc.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
Index: doc/src/sgml/libpq.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
On the whole I vote for #4 out of these.
I attached a patch for the docs. Its documented as a NOTE to the
PGEventProc.
Applied, but I editorialized on the wording a bit. Let me know if you
think this is wrong ...
It's correct
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
That got rid of all warnings. Although, it still fails to compile due
to gethostbyname_r:
thread.c:141: too many arguments to function `gethostbyname_r'
Hmm, did you override the fact that --enable-thread-safety fails?
I've always
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
I am trying to compile libpq on HP-UX 10.20 using gcc 2.95.3, cpu is a
400MHz PA8500. I'm using the 8.3.5 tarball.
Yeah, 10.20 is a bit old and creaky, and the system headers are shy of a
load in a few places. I currently use
For cygwin builds, src/test/thread/thread_test.c needs to include
sys/param.h to get MAXHOSTNAMELEN. configure is currently failing when
--enable-thread-safety is used because of this. See attached patch
against head.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
Index
;-)
I'm actually quite indifferent to this. I just think the configure
should fail with unsupported option for platform error, which Tom says
it should be doing, or something like my patch be applied.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers
referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure:25851: $? = 1
configure: program exited with status 1
configure: failed program was:
so far: hpux 10.20, solaris 2.5.1 and cygwin builds all fail when thread
safe is enable.
--
Andrew Chernow
eSilo, LLC
every
for years; for all
the same reasons. Although its only obfuscation, it works.
--
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
only discovered this trying to build libpqtypes, which requires libpq,
on our internal build farm.
--
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
Who anyone be opposed to ssldir = path as a connection option?
Currently, there is no way to change the homedir method ~/.postgresql
... or am I missing something? I am willing to supply a patch.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers
Alex Hunsaker wrote:
On Fri, Dec 5, 2008 at 13:58, Andrew Chernow [EMAIL PROTECTED] wrote:
Who anyone be opposed to ssldir = path as a connection option? Currently,
there is no way to change the homedir method ~/.postgresql ... or am I
missing something? I am willing to supply a patch.
You
it is something rather simple to design/implement (probably use a table
of user allowed queries, support regex matches, etc.. loaded at session startup
and SIGHUP).
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Grzegorz Jaskiewicz wrote:
On 2008-12-06, at 18:21, Andrew Chernow wrote:
Looking for a way to limited a user to a specific set of queries. I
don't think this can be done right now ... or can it? Has this
feature request surfaced in the past?
I currently need this as an extra security
Grzegorz Jaskiewicz wrote:
On 2008-12-06, at 18:30, Andrew Chernow wrote:
Grzegorz Jaskiewicz wrote:
On 2008-12-06, at 18:21, Andrew Chernow wrote:
Looking for a way to limited a user to a specific set of queries. I
don't think this can be done right now ... or can it? Has this
feature
the question is: is the OP
suggesting how one could be done and if so, does it make it safe to
allow ssl connections from $WORLD.
merlin
On 12/7/08, Hannu Krosing [EMAIL PROTECTED] wrote:
On Sat, 2008-12-06 at 13:30 -0500, Andrew Chernow wrote:
Grzegorz Jaskiewicz wrote:
On 2008-12-06, at 18:21, Andrew
Andrew Dunstan wrote:
Andrew Chernow wrote:
I think what is missing is a way to deny the execution of queries that
don't operate on an object (like a table, sequence, role, schema,
etc...), OR queries not covered by the priv system. Object-based
queries can be locked down using
Andrew Dunstan wrote:
Andrew Chernow wrote:
I think what is missing is a way to deny the execution of queries that
don't operate on an object (like a table, sequence, role, schema,
etc...), OR queries not covered by the priv system. Object-based
queries can be locked down using
:
A thread in an executable that calls the C run-time library (CRT) should use
the _beginthread and _endthread functions for thread management rather than
CreateThread and ExitThread;
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql
a CloseHandle on ret_child anywhere. The HANDLE still exists after
the thread exists, you still have to call CloseHandle.
--
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:
HANDLE h = (HANDLE)_beginthreadex(NULL, 0, thread_start, arg, 0, NULL);
This didn't give me any more joy, unfortunately. But you're right, I
should be using it.
Are these threads sharing memory, intentionally or by mistake?
Things
copied at line 315 of your patch,
where you prepare the RestoreArgs struct for the thread. Every thread
is accessing and possibly updating the members of these structs that
need to be deep copied.
Forgot something, the prestore function leaks the RestoreArgs struct.
--
Andrew Chernow
eSilo, LLC
Magnus Hagander wrote:
* Renamed PGROOTCERT to PGSSLROOTCERT
+primaryenvarPGROOTCERT/envar/primary
Looks like the old env name is still being used in the sgml docs.
I like the flexibility this patch offers.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com
the above
error? The non-windows path is safe from this because a) it never does
an fclose and b) its a fork and has its own copy of the FH.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
but apparently I need food :)
--
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
thread and comment out any
in-thread deep copying. I wonder if that would work with no other changes.
--
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
. Maybe you can get away with only copying some of the
members (trial-n-error), I don't think they are all being used in this context.
Nothing should be copied from within the thread itself.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list
something. It can be deprecated in favor of a
cleaner and more elagant method.
My two cents ... I never use CREATE TYPE AS, seems redundant and
limited. I use CREATE TABLE and just never insert any records.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql
purposes, but I think that would lead to ambiguity with dollar quoting.
Would this be limited to sql functions? I only ask because for non-sql
functions we currently prefix parameter names with an underscore, but a built-in
special marker would be much more desirable.
--
Andrew Chernow
eSilo
like $abc$def, where abc and def are
variables. Although, this is much less likely than column name conflicts.
Other possibles are: $(var), @var@, or %var%. I'd perfer a single character
marker but that may not fly.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent
via $1 and $1. Making '$' a marker for parameters
wouldn't introduce it.
--
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
.
(But having said that, an alternate qualification name is something
that could be implemented if there were any agreement on what to use.)
Would something like ARG.name be acceptable?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list
Tom Lane wrote:
Andrew Chernow a...@esilo.com writes:
Tom Lane wrote:
(But having said that, an alternate qualification name is something
that could be implemented if there were any agreement on what to use.)
Would something like ARG.name be acceptable?
It all depends on how likely you
--
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
it knows it should rescan the original data
and rebuild the cache and not just serve invalid data.
That's far more complicated than throwing an error and it discards user payload
information. Let the error indicate a rescan is needed.
--
Andrew Chernow
eSilo, LLC
every bit counts
http
via GUC:
drop-oldest (as above)
drop-largest (if we run out of room, drop the largest payloads first to
save space)
error (if we run out of room, error and rollback)
I mentioned this up thread. I completely agree that overflow behavior should be
tunable.
--
Andrew Chernow
eSilo, LLC
every bit
Tom Lane wrote:
Andrew Chernow a...@esilo.com writes:
I mentioned this up thread. I completely agree that overflow behavior should be
tunable.
There is only one correct overflow behavior.
I count three.
1. wait
2. error
3. skip
#1 and #2 are very similar to a file system. If FS buffers
Tom Lane wrote:
Andrew Chernow a...@esilo.com writes:
Tom Lane wrote:
There is only one correct overflow behavior.
I count three.
Waiting till you can insert is reasonable (especially if we have some
behavior that nudges other backends to empty the queue). If by skip
you mean losing
conversion problems in some circumstances - what about bytea (or why
_do_ we have to limit this to something?).
I agree with bytea. Zero conversions and the most flexible. Payload
encoding/format should be decided by the user.
--
Andrew Chernow
eSilo, LLC
every bit counts
http
with libpq.
--
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
of
appending _t to such beasts.
I'll just throw a little meat into the pack wolvesconstraints?
--
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
Peter Eisentraut wrote:
On mån, 2010-01-11 at 15:02 -0500, Andrew Chernow wrote:
ISTM that the ultimate would be a 'create table (_) without storage'
(or some'm) and make 'create type' an alternate syntax for SQL
conformance.
I don't really understand the purpose of that.
What
Peter Eisentraut wrote:
On mån, 2010-01-11 at 19:27 -0500, Andrew Chernow wrote:
Peter Eisentraut wrote:
On mån, 2010-01-11 at 15:02 -0500, Andrew Chernow wrote:
ISTM that the ultimate would be a 'create table (_) without storage'
(or some'm) and make 'create type' an alternate syntax
sneer :) Honestly, I
was only trying to understand why it existed.
--
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
9.0.
You don't have a code-name. All the cool kids have code-names for their
projects.
Black Dog
yup, I'm a zeppelin fan :)
--
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
postgresql more popular, however silly that may seem, then I am all for it.
This is a difficult marketing decision.
--
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.mail-archive.com/pgsql-hackers@postgresql.org/msg128603.html
--
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
be an alternative? NOTE: I may have missed this
discussion. Sorry if it has already been covered.
--
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
the
driver will implement the new feature ... JDBC seems to lack the ability to get
the backing Socket object but java can set socket options. Maybe a JDBC kong fu
master knows how to do this.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list
, JDBC, etc... all enable or disable keepalives by default. I
only bring this up because it appears there are complaints from
non-libpq clients. This patch wouldn't fix those cases.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql
approval. Otherwise, anyone
with an idea would be a committer.
--
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
What does SELECT 2 * '3'::money; do?
That works.
try changing 64 to 32 in the function cash_mul_int4
That also worked.
Datum
cash_mul_int4(PG_FUNCTION_ARGS)
{
Cashc = PG_GETARG_CASH(0);
/*int64 i = PG_GETARG_INT64(1);*/
int32 i =
= PG_GETARG_INT32(1); just like cash_mul_int4().
Andrew
Andrew Chernow wrote:
What does SELECT 2 * '3'::money; do?
That works.
try changing 64 to 32 in the function cash_mul_int4
That also worked.
Datum
cash_mul_int4(PG_FUNCTION_ARGS)
{
Cashc = PG_GETARG_CASH(0);
/*int64
Version 0.4 of libpq param put and PGresult get functions.
Added support for inet and cidr, couple bug fixes. If you compile the
test file, make sure you link with the patched libpq.so.
Andrew
pg_param.tgz
Description: application/compressed
---(end of
Version 0.4 of libpq param put and PGresult get functions.
Added support for inet and cidr, couple bug fixes. If you compile the
test file, make sure you link with the patched libpq.so.
Andrew
pg_param.tgz
Description: application/compressed
---(end of
WINVER to the same
value as well.
--
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
on one of our ESXi servers. I'll look into
it tomorrow, not supposed to be working today ;)
--
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
*PQconnectOptions(const PGoption *options, int nOptions);
any one have a preference here?
I like the struct approach. I personally prefer specifying the element count of
an array, rather than using a NULL terminating element.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com
There is also the idea of passing an array of structs floating around,
NULL terminated list or include an additional argument specifying
element count.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
Jaime Casanova wrote:
On Mon, Sep 14, 2009 at 1:34 PM, Andrew Chernow a...@esilo.com wrote:
Jaime Casanova wrote:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding from client locale and put it in
libpq so i follow the PQconnectdbParams
to be cute but that apparently failed :(
--
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
;)
--
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
with the PIC option (gcc -fPIC, sun compiler -Kpic).
--
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
David Fetter wrote:
Folks,
I'd like to see about creating man pages for the following:
- libpq
- SPI
- the built-in functions
That would be really helpful and convenient. I've often wanted libpq man pages.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via
supporting that argument, solaris 10 threads vs. linux
2.6.11+ kernel (p)threads?
Another thing to consider in your decision is that Sun was just bought by
oracle, leaving the solaris road map up in the air. At least for me, Linux is a
bit more reassuring ... or freebsd.
--
Andrew Chernow
eSilo
Zdenek Kotala wrote:
Andrew Chernow píše v ne 18. 10. 2009 v 21:09 -0400:
I'm curious if this is a lost hope. My boss is recommending we flatten
the Sun box and install redhat linux (which I'm fine with). I'd rather
not as threading in Solaris is better.
Maybe solaris threads were better 10
1 - 100 of 332 matches
Mail list logo
