Bruce Momjian wrote:
>
> Thanks. Interesting. Hard to imagine what they were thinking when they
> put this code in.
Way back in the day, when dinosaurs ruled the earth, or at least the
server room, many applications were written with rather bad memory
allocation semantics: they'd grab a bunch o
Once more unto the breach -
Could you please abstain from sending HTML email to the list ?
Many thanks !
--
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
> > Surely PHP can be modified so as to use the new 3.0 protocol feature to
> > detect whether it's in a transaction or not, so as to avoid unnecssary
> > querying?
>
> Yes, you could, but it hardly seems worth it because they have to
> support old and new protocols. Eventually, yes, they could us
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> In hba.c, line 1394 is missing two )
Yeah, my fault :-(. Should be fixed as of a few hours ago --- do you
see any others?
regards, tom lane
---(end of broadcast)---
TIP 7: don't for
On Wed, 23 Jul 2003, Christopher Kings-Lynne wrote:
> > > I mean, the end user - the person entering the search string on the
> website
> > > won't know that syntax...
> >
> > You always could rewrite user query to that syntax.
>
> That's why I said it would be a cool feature! Saves every web des
Marcus B?rger wrote:
> >> However it may be very usefull to terminate any open transaction before
> >> reusing a persisten connection. Typically this happens when the same script
> >> runs again. But anyway using transactions together with persistent conenctions
> >> in a multithreaded environment
Christopher Kings-Lynne wrote:
> > > DEBUG: InitPostgres
> > > DEBUG: StartTransactionCommand
> > > DEBUG: query: select getdatabaseencoding()
> > > DEBUG: ProcessQuery
> > > DEBUG: CommitTransactionCommand
> > > DEBUG: StartTransactionCommand
> > > DEBUG: query: RESET ALL
> > > DEBUG: Proc
Hauke Joachim Zuehl <[EMAIL PROTECTED]> writes:
> I want to compile a program which uses libpq-fe.h but it seems that
> structure pg_conn ist not declared.
The typedef is named PGconn.
regards, tom lane
---(end of broadcast)
But the snapshots only are grabbing the xids from each proc, right?
Doesn't seem that would take very long.
If this is the bottleneck, maybe we need a shared proc lock.
I had a hard day testing and verifying this kind of stuff. We have run
several hundred benchmarks at the customer using many
Hello Bruce,
Tuesday, July 22, 2003, 3:20:27 AM, you wrote:
BM> Jan Wieck wrote:
>> Bruce Momjian wrote:
>> > Marcus B?rger wrote:
>> >> BM> Marcus, would you check if PHP is using RESET ALL when passing
>> >> BM> persistent connection to new clients? We added that capability a few
>> >> BM> rel
Hello Jan,
Tuesday, July 22, 2003, 1:28:18 PM, you wrote:
JW> Marcus Börger wrote:
>>
>> Here's the current log while reusing the persistent connection:
>>
>> DEBUG: InitPostgres
>> DEBUG: StartTransactionCommand
>> DEBUG: query: select getdatabaseencoding()
>> DEBUG: ProcessQuery
>> DEBUG:
I mean, what is getting buffered? What performance effects is it supposed allow?
Nailah Ogeer wrote:
Hello,
I have written code to support multiple buffer pools in postgres 7.3.2.
Now i am looking at changing the sizes of these buffer pools, but first i
need to write all pages to disk.
I also nee
pool of what?
Nailah Ogeer wrote:
Hello,
I have written code to support multiple buffer pools in postgres 7.3.2.
Now i am looking at changing the sizes of these buffer pools, but first i
need to write all pages to disk.
I also need to incorporate this code into the backend instead of it being
a s
Hello Bruce,
Tuesday, July 22, 2003, 10:16:53 PM, you wrote:
BM> Marcus B?rger wrote:
>> Yeah well it seems i gave a wrong impression what is actually happening now.
>> We don't handle any transaction at the moment but starting with the second
>> call to pg_pconnect on the same db we do RESET ALL
Hello Bruce,
Tuesday, July 22, 2003, 11:26:32 PM, you wrote:
BM> I see autocommit as implemented only in psql, not in libpq. Is that
BM> what we want to do for 7.4?
Autocommit with libpq could be a good idea for web applications, especially
when not so expirienced users connect from a scriptin
Hi there,
is't possible to specify default search path for dbh in DBD::Pg ?
I don't want to set variable before every select.
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astron
Hello Jan,
Tuesday, July 22, 2003, 10:57:56 PM, you wrote:
JW> Bruce Momjian wrote:
>> Marcus B?rger wrote:
>>> However it may be very usefull to terminate any open transaction before
>>> reusing a persisten connection. Typically this happens when the same script
>>> runs again. But anyway using
On Wed, 23 Jul 2003, Christopher Kings-Lynne wrote:
> > > SELECT intindex, strtopic FROM tblmessages
> > > WHERE idxfti @@ 'jam and
> > > toast -guitar'::userquery::tsquery;
> >
> > idxfti @@ 'jam & toast & ! guitar'
>
> I mean, the end user - the person entering
They do the backend protocol using a custom implementation. Why would
they do that?
It seems as if their implemenation provides 20% more throughput. I
haven't benchmarked with lib pq personally so I cannot tell you more.
Hans
--
Cybertec Geschwinde u Schoenig
Ludo-Hartmannplatz 1/14, A-1160
> > I mean, the end user - the person entering the search string on the
website
> > won't know that syntax...
>
> You always could rewrite user query to that syntax.
That's why I said it would be a cool feature! Saves every web designer from
writing the conversion code for their site - you just p
Thanks. Interesting. Hard to imagine what they were thinking when they
put this code in.
---
Andrew Dunstan wrote:
> The current developer docs say this:
>
> ---
> Linux has poor default memory overcommit
Andrew Dunstan wrote:
Rather than give bad advice, it might be better to advise users (1) to run
Pg on machines that are likely to be stable and not run into OOM situations,
and (2) to check with their vendors about proper overcommit handling.
Would it be possible (or trivial?) to write a small C
> II) SQL
> ---
>
> The first idea is to ask SQL to do the job with a 'group by' clause:
>
> SELECT area, type, month, SUM(amount), COUNT(*)
> FROM client AS c, invoice AS i
> WHERE c.id=i.client
> GROUP BY area, type, month;
>
> As I am just interested in reading the data, without any transact
Hello :)
I want to compile a program which uses libpq-fe.h but it seems that
structure pg_conn ist not declared.
I have SuSE 8.2 and postgresql-devel-7.3.2-42
Thanks for any hints :)
Kind regards,
Hauke
--
Aus Ben Hur (1959): Wer nicht fuer Rom ist, ist gegen Rom
George W. Bush (2002): Wer nic
Iam trying to acquire rowlevel locks in postgresql. I try doing this:
'select * from students where name='Larry' for update;
But by looking at the holding array of proclock , I've noticed that by doing this only
AccessShareLock gets acquired which is a table level lock.
How do I acquire r
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
I just checked out (at the moment hba.c changed, so I had to redo it),
make clean, make, pgsql stop, make install, pgsql start and it's still
there.
It works fine for me too. Try removing
src/backend/parser/gram.c and src/backen
> > SELECT intindex, strtopic FROM tblmessages
> > WHERE idxfti @@ 'jam and
> > toast -guitar'::userquery::tsquery;
>
> idxfti @@ 'jam & toast & ! guitar'
I mean, the end user - the person entering the search string on the website
won't know that syntax...
Chris
> > DEBUG: InitPostgres
> > DEBUG: StartTransactionCommand
> > DEBUG: query: select getdatabaseencoding()
> > DEBUG: ProcessQuery
> > DEBUG: CommitTransactionCommand
> > DEBUG: StartTransactionCommand
> > DEBUG: query: RESET ALL
> > DEBUG: ProcessUtility: RESET ALL
> > DEBUG: CommitTransac
Andreas Pflug <[EMAIL PROTECTED]> writes:
> I just checked out (at the moment hba.c changed, so I had to redo it),
> make clean, make, pgsql stop, make install, pgsql start and it's still
> there.
It works fine for me too. Try removing
src/backend/parser/gram.c and src/backend/parser/parse.h
t
Joe Conway wrote:
Andreas Pflug wrote:
The current snapshot won't initdb, because running
information_schema.sql fails.
The two occurences of "WHERE u.usesysid = ANY( g.grolist )" are the
problem. Replacing the ANY clause with some dummy will let everything
run ok.
select usename from pg_user
In hba.c, line 1394 is missing two )
if (pass == NULL)
{
ereport(LOG,
(errmsg("local user with uid %d is not known to
getpwuid",
(int) peercred.uid);
Andreas Pflug wrote:
The current snapshot won't initdb, because running
information_schema.sql fails.
The two occurences of "WHERE u.usesysid = ANY( g.grolist )" are the
problem. Replacing the ANY clause with some dummy will let everything
run ok.
select usename from pg_user, pg_group where use
Marcus B?rger wrote:
> Hello Jan,
>
> Tuesday, July 22, 2003, 10:57:56 PM, you wrote:
>
> JW> Bruce Momjian wrote:
> >> Marcus B?rger wrote:
> >>> However it may be very usefull to terminate any open transaction before
> >>> reusing a persisten connection. Typically this happens when the same scr
The current developer docs say this:
---
Linux has poor default memory overcommit behavior. Rather than failing if it
can not reserve enough memory, it returns success, but later fails when the
memory can't be mapped and terminates the application with kill -9. To
prevent unpredict
I see autocommit as implemented only in psql, not in libpq. Is that
what we want to do for 7.4?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be yo
> This allows functions to read/write operating system files. Is this of
> interest to anyone?
Is this something that requires untrusted status, as it would if I
wrote a function in perl to do the same thing?
--
Mike Nolan
---(end of broadcast)---
Bruce Momjian wrote:
Marcus B?rger wrote:
However it may be very usefull to terminate any open transaction before
reusing a persisten connection. Typically this happens when the same script
runs again. But anyway using transactions together with persistent conenctions
in a multithreaded environment
This allows functions to read/write operating system files. Is this of
interest to anyone?
---
ivan wrote:
>
> if you want to see this , there is the src :
> http://www.psycho.pl/public/src/pgsql/files.tar.bz2
>
> and sam
On Tue, 22 Jul 2003, Francisco Figueiredo Jr. wrote:
> > How's this for an alternative if you really don't want any rows returned:
> >
> > create function fincF ( ) returns setof integer as '
> > begin
> >delete from blah;
> >return;
> > end;
> > ' language 'plpgsql';
> >
> >
>
> T
hi
what do you tink about :
COPY [ namespace1. ] table [ STRUCT ONLY ] TO [namespace2.] table2;
MOVE [ namepsace1. ] table TO [namespace2.] table2;
and this same whit types, functions etc
and :
ALERT FUNCTION func (ARGS) SET OWNER new_owner;
and :
CREATE TYPE new_type AS table;
this can by r
Nigel J. Andrews wrote:
On Tue, 22 Jul 2003, Francisco Figueiredo Jr. wrote:
select * from funcF();
Yeap, it works, but you specified integer as the return type :)
Yes, that's because I knew the void wouldn't work. :]
:)
How's this for an alternative if you really don't want any rows return
I assume this will not be completed for 7.4. I will keep the emails for
7.5.
One idea I had was to use the existing sort_mem parameter to control
when to force the deferred trigger queue to disk --- it doesn't have
anything to do with sorting, but it does have the same purpose, to force
thing to
if you want to see this , there is the src :
http://www.psycho.pl/public/src/pgsql/files.tar.bz2
and sample
On Mon, 21 Jul 2003, Bruce Momjian wrote:
>
> I haven't seen those myself.
>
> ---
>
> ivan wrote:
> >
> > function
On Tue, 22 Jul 2003, Francisco Figueiredo Jr. wrote:
> > select * from funcF();
> >
>
> Yeap, it works, but you specified integer as the return type :)
Yes, that's because I knew the void wouldn't work. :]
>
> I'd like to have the return type as void and be possible to call it with
> select *
Well, it seems it would be easier for them to just improve our existing
libpq and send us the patches, rather than rewriting it from scratch.
---
Hans-Jürgen Schönig wrote:
> > They do the backend protocol using a custom imp
Marcus B?rger wrote:
> Yeah well it seems i gave a wrong impression what is actually happening now.
> We don't handle any transaction at the moment but starting with the second
> call to pg_pconnect on the same db we do RESET ALL. The following log is from
> a three connections, so you can see two
On Tue, Jul 22, 2003 at 04:05:46PM -0300, The Hermit Hacker wrote:
>
> Did I miss part of a thread here? :)
I don't think so. Josh was responding to my post, id
19f22n-0007Gm-00.
A
--
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toro
Nigel J. Andrews wrote:
Try returning an integer but returning a null for that integer...on the other
hand I see you're using sql as the language and I don't know how that would
work.
I tried that and it works. I changed the function body to do a query
which returns null. The problem only appe
On Tue, 22 Jul 2003, Francisco Figueiredo Jr. wrote:
>
> Hi all,
>
> I would like to know why does calling a function with select * from
> function doesn't work when its return type is set to void.
>
> I'm asking this because I have a code which uses this syntax to add
> support for returning
On Tue, 22 Jul 2003, Fabien COELHO wrote:
> ...
>
> III) PL/pgSQL
> -
>
> Ok, if postgresql does not want to do it my way, let us make it do it.
> Thus I wrote some PL/pgSQL function for my purpose, something like:
>
> CREATE TEMPORARY TABLE tmp (
> area INTEGER,
> type INTEGER,
Hi all,
I would like to know why does calling a function with select * from
function doesn't work when its return type is set to void.
I'm asking this because I have a code which uses this syntax to add
support for returning resultsets from functions. This way, regardless
the function returns
Did I miss part of a thread here? :)
On Tue, 22 Jul 2003, Josh Berkus wrote:
> Andrew,
>
> > Arguments? None of those three address the obvious marketing benefit
> > of having replication shipping with the main tarball, I know.
>
> Those are pretty strong arguments ... and we can't let Postgre
Yes, but you probably want old clients to be able to use the new nested
transaction code.
---
Rod Taylor wrote:
-- Start of PGP signed section.
> > > Won't that break when we have nested transactions implemented? i.e.
> >
Andrew,
> Arguments? None of those three address the obvious marketing benefit
> of having replication shipping with the main tarball, I know.
Those are pretty strong arguments ... and we can't let PostgreSQL new
"marketing awareness" sway us to the point that we start making technically
unfea
On Tue, Jul 15, 2003 at 04:19:34PM -0400, Andrew Sullivan wrote:
> I thought that now would be a good time to ask whether it should
> live as a separate project, or whether it should be in contrib. I
I have run into a number of arguments for putting the project on
gborg. Unless I hear strong ar
Peter Eisentraut wrote:
> I've been thinking some about how exactly to provide the new option of
> thread-safe clients (libpq, ecpg). Let me state the following goals:
>
> a. Thread-safeness, where it makes a difference, is generally thought to
> be a performance hit, so the user needs to have a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> But the snapshots only are grabbing the xids from each proc, right?
> Doesn't seem that would take very long.
Yeah, we've never seen any previous indication that grabbing a snapshot
is a bottleneck. Also, I think it uses a shared (read) lock, so there
Hello,
I have written code to support multiple buffer pools in postgres 7.3.2.
Now i am looking at changing the sizes of these buffer pools, but first i
need to write all pages to disk.
I also need to incorporate this code into the backend instead of it being
a sql statement as it is now. I noticed
> > Won't that break when we have nested transactions implemented? i.e.
> > begin;commit; would just open a sub transaction and have no effect on the
> > outer transaction...
>
> Yes, it would break. I am not sure how we are going to flag that we
> want to rollback all nested transactions, may
> You want to process all invoices to count them
> and to sum up the amounts on a per month/area/type
> basis. The initial data size is in GB, but the
> size of the expected result is in KB (namely 2 data
> for each 100 areas * 12 months * 4 types).
The key to handling large datasets for data min
On Tue, Jul 22, 2003 at 18:39:33 +0200,
Fabien COELHO <[EMAIL PROTECTED]> wrote:
>
> As the resulting table is very small, I wish the optimizer would have
> skipped the sort phase, so as to aggregate the data as they come after the
> join. All may be done on the fly without much additionnal stor
Thomas Swan wrote:
> >>Oh, I remember that now as part of the persistent connection code. As I
> >>remember, we told them to do BEGIN;COMMIT; to clear any open transaction
> >>state passed to the new client. Is that in there? If not, it has to be
> >>added too. ROLLBACK will generate an error i
The current snapshot won't initdb, because running
information_schema.sql fails.
The two occurences of "WHERE u.usesysid = ANY( g.grolist )" are the
problem. Replacing the ANY clause with some dummy will let everything
run ok.
select usename from pg_user, pg_group where usesysid = ANY (grolist)
On 7/22/2003 11:18 AM, scott.marlowe wrote:
>On Mon, 21 Jul 2003, Bruce Momjian wrote:
>
>
>
>>Jan Wieck wrote:
>>
>>
>>>Bruce Momjian wrote:
>>>
>>>
Marcus B?rger wrote:
>BM> Marcus, would you check if PHP is using RESET ALL when passing
>BM> persistent c
FYI, we are currently scheduled for beta on Monday. Tom and I are both
still cleaning up things.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be y
Josh Berkus wrote:
> Hans, Bruce,
>
> We're drafting the press release for 7.4 right now. What's the odds that
> dblink_ora will be ready in time for 7.4?
There seems to be some disagreement on whether the Oracle lib checks
should be in configure for a /contrib module, and I don't know how far
Hans-Jürgen Schönig wrote:
> > But the snapshots only are grabbing the xids from each proc, right?
> > Doesn't seem that would take very long.
> >
> > If this is the bottleneck, maybe we need a shared proc lock.
> >
>
>
> I had a hard day testing and verifying this kind of stuff. We have run
Peter Eisentraut wrote:
> I have a few problems with the file threads.c:
>
> 1. It doesn't contain any threads, so the name is slightly inappropriate.
>
> 2. It's not a porting module (since pqStrerror, etc. are not system
> functions), so it doesn't belong into src/port.
>
> 3. It's only used b
Dear PostgreSQL developers,
I have considered postgresql for data-mining, and I would like to
share some comments on the issues involved, that result in several
specific suggestions for improvements in various areas. I've notice
that some of the issues seems listed in the todo list, so it may be
Peter Eisentraut wrote:
> I have two questions about the support for thread-safe clients in
> configure:
>
> configure sets NEED_REENTRANT_FUNC_NAMES=no, overwriting the template
> setting. Why?
Forgot to remove it when I moved the stuff to templates.
> The check for reentrant functions says:
scott.marlowe wrote:
> > > It does generate the usual error if the current transaction block is in
> > > ABORT state. So the correct querystring to send would be something like
> > >
> > > "ROLLBACK; RESET ALL"
> >
> > Oh, I remember that now as part of the persistent connection code. As I
On Mon, 21 Jul 2003, Bruce Momjian wrote:
> Jan Wieck wrote:
> > Bruce Momjian wrote:
> > > Marcus B?rger wrote:
> > >> BM> Marcus, would you check if PHP is using RESET ALL when passing
> > >> BM> persistent connection to new clients? We added that capability a few
> > >> BM> releases ago, speci
Hans, Bruce,
We're drafting the press release for 7.4 right now. What's the odds that
dblink_ora will be ready in time for 7.4?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 5: Have you checked our extensive
Tom Lane writes:
> Lee Kindness <[EMAIL PROTECTED]> writes:
> > I'd have to disagree with regards to the memory leaks not being worth
> > a mention - any such leak can cause problems when the PostgreSQL
> > installation is either unattended, long-living andor has very high
> > connection level
Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > OK. I'll suggest people to try new tsearch2 in README file of old
> > tsearch.
>
> Okay, that works for me. Please patch the old tsearch README file in
> both HEAD and REL7_3_STABLE branch as soon as possible --- we are going
> to wr
Patched.
Tom Lane wrote:
Oleg Bartunov <[EMAIL PROTECTED]> writes:
OK. I'll suggest people to try new tsearch2 in README file of old
tsearch.
Okay, that works for me. Please patch the old tsearch README file in
both HEAD and REL7_3_STABLE branch as soon as possible --- we are going
to wrap a 7
Tom Lane wrote:
> =?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> > There is one nifty detail which seems VERY strange to me: If
> > serializable mode is set in postgresql.conf the system was 3 times
> > faster (~ 7.5 sec. vs. 2.5sec). If serializable mode was set for every
On 22 Jul 2003 at 16:55, Peter Eisentraut wrote:
> I've been thinking some about how exactly to provide the new option of
> thread-safe clients (libpq, ecpg). Let me state the following goals:
>
> a. Thread-safeness, where it makes a difference, is generally thought to
> be a performance hit, so
As I was documenting my current project the other day, a couple of things
occurred to me:
1. It would be nice to be able to dump my schema in some XML format that I
could then process using XSLT into whatever format I desired. If there is
not already some easy way to do this, and there is interes
--On Tuesday, July 22, 2003 11:11:33 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
I've been thinking some about how exactly to provide the new option of
thread-safe clients (libpq, ecpg). Let me state the following goals:
Sounds good to me. Do you hav
On Tue, Jul 22, 2003 at 10:31:36AM -0400, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > ./configure --prefix=/usr/lib/postgresql --enable-nls
>
> I think you must have done --enable-recode too.
Oops.. you're right :-)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.z
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I've been thinking some about how exactly to provide the new option of
> thread-safe clients (libpq, ecpg). Let me state the following goals:
Sounds good to me. Do you have time to make these things happen?
regards, tom lane
On Tue, 22 Jul 2003, Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > OK. I'll suggest people to try new tsearch2 in README file of old
> > tsearch.
>
> Okay, that works for me. Please patch the old tsearch README file in
> both HEAD and REL7_3_STABLE branch as soon as possible --
Lee Kindness <[EMAIL PROTECTED]> writes:
> I'd have to disagree with regards to the memory leaks not being worth
> a mention - any such leak can cause problems when the PostgreSQL
> installation is either unattended, long-living andor has very high
> connection levels.
I don't see how. We are tal
I've been thinking some about how exactly to provide the new option of
thread-safe clients (libpq, ecpg). Let me state the following goals:
a. Thread-safeness, where it makes a difference, is generally thought to
be a performance hit, so the user needs to have a choice to use
thread-safe librarie
Karel Zak <[EMAIL PROTECTED]> writes:
> ./configure --prefix=/usr/lib/postgresql --enable-nls
I think you must have done --enable-recode too.
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations
> -I../../../../src/include -c -o miscinit.o miscinit.c -MMD
> miscinit.c: In function `Set
Tom, happier with the attached patch?
I'd have to disagree with regards to the memory leaks not being worth
a mention - any such leak can cause problems when the PostgreSQL
installation is either unattended, long-living andor has very high
connection levels. Half a kilobyte on start-up isn't negli
Lee Kindness <[EMAIL PROTECTED]> writes:
> Guys, attached is a patch to fix two memory leaks on start-up.
I do not like the changes to miscinit.c. In the first place, it is not
a "memory leak" to do a one-time allocation of state for a proc_exit
function. A bigger complaint is that your proposed
On Tue, 2003-07-22 at 09:06, Merlin Moncure wrote:
> I looked on the to-do list and noticed adding check constraints to
> domains is not on it. IMO, being able to add a validation constraint
> is one of the very best things about domains. Is anybody planning to
> work on this?
7.4 has descent
./configure --prefix=/usr/lib/postgresql --enable-nls
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../../src/include -c -o miscinit.o miscinit.c -MMD
miscinit.c: In function `SetCharSet':
miscinit.c:205: error: structure has no member named `in'
make[3]: *** [miscinit.o]
I looked on the to-do list and noticed adding check
constraints to domains is not on it.
IMO, being able to add a validation constraint is one of the very best
things about domains. Is anybody planning to work on this?
Regards,
Merlin
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> OK. I'll suggest people to try new tsearch2 in README file of old
> tsearch.
Okay, that works for me. Please patch the old tsearch README file in
both HEAD and REL7_3_STABLE branch as soon as possible --- we are going
to wrap a 7.3.4 release as soon as
Christopher Kings-Lynne wrote:
I think it's production quality. Actually, we use it in our
projects with 7.3.3. You may read docs on tsearch2 home page
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/
You know what would be an AWESOME feature? The ability to process user
queries directly
Marcus Börger wrote:
Here's the current log while reusing the persistent connection:
DEBUG: InitPostgres
DEBUG: StartTransactionCommand
DEBUG: query: select getdatabaseencoding()
DEBUG: ProcessQuery
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: RESET ALL
DEBUG
It was in libpq in my original patch, not port.
L.
Peter Eisentraut writes:
> I have a few problems with the file threads.c:
>
> 1. It doesn't contain any threads, so the name is slightly inappropriate.
>
> 2. It's not a porting module (since pqStrerror, etc. are not system
> functions),
Guys, attached is a patch to fix two memory leaks on start-up. The
first is when freeaddrinfo has been used to free memory allocated by
getaddrinfo2 (so freeaddrinfo2 should be used). The second is 2 leaks
when creating the lock (PostgreSQL and socket) files.
The diff is against last night's CVS H
I have a few problems with the file threads.c:
1. It doesn't contain any threads, so the name is slightly inappropriate.
2. It's not a porting module (since pqStrerror, etc. are not system
functions), so it doesn't belong into src/port.
3. It's only used by libpq, so why not put it into the libp
I have two questions about the support for thread-safe clients in
configure:
configure sets NEED_REENTRANT_FUNC_NAMES=no, overwriting the template
setting. Why?
The check for reentrant functions says:
# Include special flags if threads are enabled _and_ if required for
# threading on this platf
> I think it's production quality. Actually, we use it in our
> projects with 7.3.3. You may read docs on tsearch2 home page
> http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/
You know what would be an AWESOME feature? The ability to process user
queries directly:
eg.
SELECT intindex, str
100 matches
Mail list logo
