<[EMAIL PROTECTED]> writes:
> This analysis makes sense - I think using memcmp is clearly wrong here.
Yeah, now that I think about it, we're betting on the kernel to
faithfully zero all unused bits in addrinfo structures. In an ideal
world, all kernels would do that, but in the real world it seem
This analysis makes sense - I think using memcmp is clearly wrong here.
cheers
andrew
Jan Wieck said:
> On a second thought,
>
> I still believe that this is just garbage in the padding bytes after
> the IPV4 address. The code currently bind()'s and connect()'s
> explicitly to an AF_INET addr
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I found a few notices and warnings that inform you that the command you
> are executing has no effect because the object is already in the state you
> want it. I think these are useless, and there is also some inconsistency.
> Does someone want to def
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Robert Treat writes:
>> In all this discussion of NOTICE vs. WARNING, can someone remind me the
>> logic for INFO? I can't seem to recall the differentiator there either.
> Info is something you request explicitly. In the past, the result for
> EXPL
Sean Chittenden <[EMAIL PROTECTED]> writes:
>>> Is it really necessary for postgres to be linked with ncurses
>>> (288K) and readline (156K)? It's .5M, not the end of the world,
>>> but it seems excessive. I know the postmaster has a CLI
>>> interface, but does it really require ncurses or readli
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Just how transient is the memory context created for a C language
> function call?
Fairly. IIRC, you'll normally be running in a context that will be
reset at the start of the next tuple cycle for the plan node your
function is evaluated by. If you'v
On Fri, 2003-09-05 at 16:54, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian writes:
> >
> > > I don't mind the maintenance. I just want people to stop getting stuck
> > > creating plpsql functions.
> >
> > Then put plpgsql in the default installation.
>
> Fine with me. I thou
On Sat, Sep 06, 2003 at 12:47:21AM +0200, Peter Eisentraut wrote:
> I found a few notices and warnings that inform you that the command you
> are executing has no effect because the object is already in the state you
> want it. I think these are useless, and there is also some inconsistency.
> Doe
I found a few notices and warnings that inform you that the command you
are executing has no effect because the object is already in the state you
want it. I think these are useless, and there is also some inconsistency.
Does someone want to defend keeping them?
=> alter table test set without oi
On 4 Sep, Manfred Spraul wrote:
> [EMAIL PROTECTED] wrote:
>
>>http://developer.osdl.org/markw/44/
>>
>>I threw together (kind of sloppily) a web page of the data I was
>>starting to collect for our DBT-2 workload (TPC-C derivative) on
>>PostgreSQL 7.3.4. Keep in mind not much database tuning has
On 6 Sep, Manfred Spraul wrote:
> Another question:
> Is it possible to apply patches to postgresql before a DBT-2 run, or is
> only patching the kernel supported?
The data I reported is from a test system I'm using in our lab, so I
can certainly try patches. The current state of STP only allow
> > > We add those to all links, mostly because it is too confusing to
> > > do it per link. It doesn't hurt anything because it is
> > > dynamically linked, so doesn't take any disk space, and in fact
> > > is never called.
> >
> > My concern wasn't for disk space, but for symbol resolution time
Sean Chittenden wrote:
> > We add those to all links, mostly because it is too confusing to do
> > it per link. It doesn't hurt anything because it is dynamically
> > linked, so doesn't take any disk space, and in fact is never called.
>
> My concern wasn't for disk space, but for symbol resoluti
Another question:
Is it possible to apply patches to postgresql before a DBT-2 run, or is
only patching the kernel supported?
--
Manfred
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
> > % ldd `which postgres`
> > /usr/local/bin/postgres:
> > libintl.so.5 => /usr/local/lib/libintl.so.5 (0x282e6000)
> > libz.so.2 => /lib/libz.so.2 (0x282ef000)
> > libreadline.so.4 => /lib/libreadline.so.4 (0x282fd000)
> > libcrypt.so.2 => /lib/libcrypt.so.2 (0x283
Robert Treat writes:
> In all this discussion of NOTICE vs. WARNING, can someone remind me the
> logic for INFO? I can't seem to recall the differentiator there either.
Info is something you request explicitly. In the past, the result for
EXPLAIN and SHOW were sent as INFO, but now those are se
Robert Treat wrote:
> On Fri, 2003-09-05 at 17:06, Peter Eisentraut wrote:
> > Neil Conway writes:
> >
> > > Should this produce a warning?
> > >
> > > nconway=# create table a (b int4 unique);
> > > NOTICE: CREATE TABLE / UNIQUE will create implicit index "a_b_key" for
> > > table "a"
> > > CREA
Sean Chittenden wrote:
> % ldd `which postgres`
> /usr/local/bin/postgres:
> libintl.so.5 => /usr/local/lib/libintl.so.5 (0x282e6000)
> libz.so.2 => /lib/libz.so.2 (0x282ef000)
> libreadline.so.4 => /lib/libreadline.so.4 (0x282fd000)
> libcrypt.so.2 => /lib/libcrypt.
Robert Treat wrote:
> On Fri, 2003-09-05 at 16:41, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Czuczy Gergely <[EMAIL PROTECTED]> writes:
> > > > It would be very nice to create a way to log only bad queries, which's
> > > > resulted in an error. This way a higher loglevel wouldn't be necessary.
% ldd `which postgres`
/usr/local/bin/postgres:
libintl.so.5 => /usr/local/lib/libintl.so.5 (0x282e6000)
libz.so.2 => /lib/libz.so.2 (0x282ef000)
libreadline.so.4 => /lib/libreadline.so.4 (0x282fd000)
libcrypt.so.2 => /lib/libcrypt.so.2 (0x28325000)
libm.so.2
On Fri, 2003-09-05 at 17:06, Peter Eisentraut wrote:
> Neil Conway writes:
>
> > Should this produce a warning?
> >
> > nconway=# create table a (b int4 unique);
> > NOTICE: CREATE TABLE / UNIQUE will create implicit index "a_b_key" for
> > table "a"
> > CREATE TABLE
> > nconway=# create table c
Peter Eisentraut wrote:
> Neil Conway writes:
>
> > Should this produce a warning?
> >
> > nconway=# create table a (b int4 unique);
> > NOTICE: CREATE TABLE / UNIQUE will create implicit index "a_b_key" for
> > table "a"
> > CREATE TABLE
> > nconway=# create table c (d int8 references a (b));
>
On Fri, 2003-09-05 at 16:41, Bruce Momjian wrote:
> Tom Lane wrote:
> > Czuczy Gergely <[EMAIL PROTECTED]> writes:
> > > It would be very nice to create a way to log only bad queries, which's
> > > resulted in an error. This way a higher loglevel wouldn't be necessary.
> >
> > We have that (might
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > If we follow Peter's recently proposed guideline, this would have to be
> > a NOTICE not a WARNING, because the command absolutely is doing what you
> > told it to do. Peter, does that make you uncomfortable?
>
> The message itself makes me a bit
Tom Lane writes:
> If we follow Peter's recently proposed guideline, this would have to be
> a NOTICE not a WARNING, because the command absolutely is doing what you
> told it to do. Peter, does that make you uncomfortable?
The message itself makes me a bit uncomfortable right now, but a NOTICE
http://developers.slashdot.org/article.pl?sid=03/09/05/1241235&mode=thread&tid=131&tid=137&tid=189&tid=198
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--On Friday, September 05, 2003 22:37:09 +0200 Peter Eisentraut
<[EMAIL PROTECTED]> wrote:
Bruce Momjian writes:
I don't mind the maintenance. I just want people to stop getting stuck
creating plpsql functions.
Then put plpgsql in the default installation.
Why don't we do that now? It would
Tom Lane writes:
> There are good security arguments not to have it in the default install,
> no?
I think last time the only reason we saw was that dump restoring would be
difficult. I don't see any security reasons.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I don't mind the maintenance. I just want people to stop getting stuck
> > creating plpsql functions.
>
> Then put plpgsql in the default installation.
Fine with me. I thought others didn't want it.
--
Bruce Momjian
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> >> Bruce Momjian writes:
> >>> I don't mind the maintenance. I just want people to stop getting stuck
> >>> creating plpsql functions.
> >>
> >> Then put plpgsql in the default installation.
>
> > Fine with
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> Bruce Momjian writes:
>>> I don't mind the maintenance. I just want people to stop getting stuck
>>> creating plpsql functions.
>>
>> Then put plpgsql in the default installation.
> Fine with me. I thought others didn't want
Neil Conway writes:
> Should this produce a warning?
>
> nconway=# create table a (b int4 unique);
> NOTICE: CREATE TABLE / UNIQUE will create implicit index "a_b_key" for
> table "a"
> CREATE TABLE
> nconway=# create table c (d int8 references a (b));
> NOTICE: CREATE TABLE will create implicit
Tom Lane wrote:
> Jeroen Ruigrok/asmodai <[EMAIL PROTECTED]> writes:
> > So I guess the problem lies in the Itanium port. Or could I miss
> > something subtle here?
>
> This strengthens my suspicion that we're not finding TAS code for
> the Itanium, but please see if you can strace or ktrace the
Bruce Momjian writes:
> I don't mind the maintenance. I just want people to stop getting stuck
> creating plpsql functions.
Then put plpgsql in the default installation.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: th
Mendola Gaetano wrote:
> "Tom Lane" <[EMAIL PROTECTED]> wrote:
> > "Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> > > "Tom Lane" <[EMAIL PROTECTED]> wrote:
> > >> I've found a number of infelicities in the hash index code that can't
> be
> > >> fixed without an on-disk format change.
> >
> > > How
Tom Lane wrote:
> Czuczy Gergely <[EMAIL PROTECTED]> writes:
> > It would be very nice to create a way to log only bad queries, which's
> > resulted in an error. This way a higher loglevel wouldn't be necessary.
>
> We have that (might be new for 7.4, I forget).
Yes, new for 7.4: log_min_error_s
Jeroen Ruigrok/asmodai <[EMAIL PROTECTED]> writes:
> So I guess the problem lies in the Itanium port. Or could I miss
> something subtle here?
This strengthens my suspicion that we're not finding TAS code for
the Itanium, but please see if you can strace or ktrace the postmaster
to verify how man
Tom Lane wrote:
I was about to say "I give up, let's just take out the comparison".
Your point is interesting but easily avoided; if we aren't going to check
fromaddr anymore then there's no need to use recvfrom(), it could as
well be recv() and save the kernel a few cycles.
Which then get's us
On 4 Sep, Manfred Spraul wrote:
> [EMAIL PROTECTED] wrote:
>
>>http://developer.osdl.org/markw/44/
>>
>>I threw together (kind of sloppily) a web page of the data I was
>>starting to collect for our DBT-2 workload (TPC-C derivative) on
>>PostgreSQL 7.3.4. Keep in mind not much database tuning has
Just how transient is the memory context created for a C language
function call?
The reason I ask is that I was getting a seg fault when I attempted to
pfree something that should have been palloced. When I commented out the
calls to pfree it worked fine. Most annoying ;-)
I'm still trying to
Bruce Momjian wrote:
Andrew Dunstan wrote:
BTW, who if anyone is rewriting initdb in C? I presume we need that for
windows so we are not dependent on having a working shell.
initdb rewrite is on my Win32 project page, but no one has offered yet.
Connx offered their version done against 7
On a second thought,
I still believe that this is just garbage in the padding bytes after the
IPV4 address. The code currently bind()'s and connect()'s explicitly to
an AF_INET address. So all we ever should see is something from and
AF_INET address. Everything else in the sin_family has to be
-On [20030905 19:12], Tom Lane ([EMAIL PROTECTED]) wrote:
>It should not; there is something wrong here, not merely a documentation
>problem. I am wondering whether your 7.4 build fails to select a TAS()
>implementation --- if so, it would fall back to implementing spinlocks
>as semap
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> BTW, who if anyone is rewriting initdb in C? I presume we need that for
> windows so we are not dependent on having a working shell.
Not me ;-). Peter replaced a bunch of other scripts with C code for
7.4, but I dunno if he intends to tackle initdb.
Jan Wieck <[EMAIL PROTECTED]> writes:
> I still believe that this is just garbage in the padding bytes after the
> IPV4 address.
Yes. I have been looking at the behavior on my own Linux box, on which
it turns out stats are broken too in CVS tip. It is very clear that
getsockname() is returning
Robert Treat <[EMAIL PROTECTED]> writes:
> On Thu, 2003-09-04 at 21:14, Bruce Momjian wrote:
>> Should we be using the pager for \h output?
> in 7.3.4 we do, let me check 7.4...seems to work, though I am on beta1
> on this box.
Hmm. I do not see the pager used for \h in either version, though it
Jan Wieck <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I was about to say "I give up, let's just take out the comparison".
> Which then get's us back to your concern about assuming that HPUX and
> Linux manpages can be taken as "every platform will" and hope all
> kernels will limit the send
-On [20030905 20:52], Tom Lane ([EMAIL PROTECTED]) wrote:
>Alternatively, find out what symbols your compiler predeclares.
>If my theory is right then your pg_config_os.h file is failing to
>define HAS_TEST_AND_SET; why?
Indeed, pg_config_os.h does not set anything for __ia64__.
Whe
Andrew Dunstan wrote:
> OK, having it comment out the line for the non-ip6 case seems safe
> enough. Having it add the line for the ip6 case would be more dangerous
> ISTM.
>
> BTW, who if anyone is rewriting initdb in C? I presume we need that for
> windows so we are not dependent on having a
well let's say that some values get crupted!
what postgres does stops the process, I want it to ignore the erro and continue importing the rest of the data into my tables and sent the error to a log file.
how could this be done.?
I really need to find a way, any sugesstions are welcome, I even t
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> BTW, duplicating the ereport is no fun. I'd suggest the coding style
>> used in some other places, with errhint called in a conditional
>> expression:
> Why does the ': 0' work? I didn't figure that would work, but it does.
The return values of the e
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
OK, now we are getting somewhere. I see that this would work. It's a bit
ugly, though - with this plan the sample file in both CVS and the
installation won't necessarily be what actually get put in place.
Well, like I said, it's
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> We could answer my objection about the hint popping out on misspelled
> >> language names if the code were to arrange to put out the hint only when
> >> the language name is one of "plpgsql", "pltcl", "pltclu", etc. This
> >> would h
Tom Lane wrote:
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> What I'm wondering about is whether we are comparing the right number of
> >> bytes ... have both address structs been reported to have the same
> >> length? Maybe we need a min().
>
> > I disagree. If getsockname(),
Jeroen Ruigrok/asmodai <[EMAIL PROTECTED]> writes:
> So it does seem 7.4 places higher demand than 7.3.4 on the SysV IPC,
It should not; there is something wrong here, not merely a documentation
problem. I am wondering whether your 7.4 build fails to select a TAS()
implementation --- if so, it wo
Jan Wieck <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What I'm wondering about is whether we are comparing the right number of
>> bytes ... have both address structs been reported to have the same
>> length? Maybe we need a min().
> I disagree. If getsockname(), getpeername() or recvfrom() r
On Thu, 2003-09-04 at 21:14, Bruce Momjian wrote:
> When I do '\h alter' in psql, the content scrolls off my screen.
>
i think you need a bigger screen
> Should we be using the pager for \h output?
>
in 7.3.4 we do, let me check 7.4...seems to work, though I am on beta1
on this box.
Robert Tr
On Fri, Sep 05, 2003 at 09:35:11AM -0400, Jan Wieck wrote:
> Redhat 7.1 says
>
>The file descriptor sockfd must refer to a socket. If the
>socket is of type SOCK_DGRAM then the serv_addr address is
>the address to which datagrams are sent by default, and
>the o
Greg Stark <[EMAIL PROTECTED]> writes:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
>> Would it be possible to catch an unconstrained max(id)/min(id) and rewrite
>> it as "select id from table order by id [desc] limit1" on the fly in the
>> parser somewhere?
>> That would require fairly little c
-On [20030905 18:32], Tom Lane ([EMAIL PROTECTED]) wrote:
>If it dies even at max_connections 10, that is a *lower* setting than we
>ever supported before (the pre-7.4 default was 32, and you need 20 or
>more to run the parallel regression test). I suspect that you actually
>don
luke wrote:
> Are there any web page or docs on win32 porting of pgsql ?
Sure:
http://candle.pha.pa.us/main/writings/pgsql/win32.html
Let me add that URL to the FAQ.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
[ CC to advocacy.]
Mendola Gaetano wrote:
> "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > The thing that slows me down the most --- trips like FOSDEM. I am doing
> > one every month or every other month. That takes 1/4 of each month.
> > The threading discussion took 1/1000 of a month, but I
Czuczy Gergely <[EMAIL PROTECTED]> writes:
> It would be very nice to create a way to log only bad queries, which's
> resulted in an error. This way a higher loglevel wouldn't be necessary.
We have that (might be new for 7.4, I forget).
> i've made some store functions in C, and it would be very
Tom Lane wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
Redhat 7.1 says
The file descriptor sockfd must refer to a socket. If the
socket is of type SOCK_DGRAM then the serv_addr address is
the address to which datagrams are sent by default, and
the only addres
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> "Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> > "Tom Lane" <[EMAIL PROTECTED]> wrote:
> >> I've found a number of infelicities in the hash index code that can't
be
> >> fixed without an on-disk format change.
>
> > How can we avoid this kind of mess for the
Are there any web page or docs on win32 porting of
pgsql ?
Regards
Luke
Jeroen Ruigrok/asmodai <[EMAIL PROTECTED]> writes:
> Using a snapshot of September the 4th:
> creating template1 database in /p/scratch/asmodai/postgresql-snapshot/src/test/r
> egress/./tmp_check/data/base/1... FATAL: could not create semaphores: No space
> left on device
> DETAIL: Failed sysca
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> We could answer my objection about the hint popping out on misspelled
>> language names if the code were to arrange to put out the hint only when
>> the language name is one of "plpgsql", "pltcl", "pltclu", etc. This
>> would have to use a hard-coded li
"Vince Vielhaber" <[EMAIL PROTECTED]> wrote:
> On Tue, 2 Sep 2003, Shridhar Daithankar wrote:
>
> > On 2 Sep 2003 at 15:50, Czuczy Gergely wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > i'm using pgsql 7.3.4.
> > > how can I fix it? i think so, i should modify the header files, i've
trie
-On [20030905 17:52], Tom Lane ([EMAIL PROTECTED]) wrote:
>Actually the bug is in beta2, not beta1. I'd suggest grabbing the
>current nightly snapshot (see /dev on the ftp servers) in preference
>to beta2, if you are on a machine with small SysV IPC limits.
Using a snapshot of Sep
"scott.marlowe" <[EMAIL PROTECTED]> writes:
> Would it be possible to catch an unconstrained max(id)/min(id) and rewrite
> it as "select id from table order by id [desc] limit1" on the fly in the
> parser somewhere?
>
> That would require fairly little code, and be transparent to the user.
>
Would it be possible to catch an unconstrained max(id)/min(id) and rewrite
it as "select id from table order by id [desc] limit1" on the fly in the
parser somewhere?
That would require fairly little code, and be transparent to the user.
I.e. low hanging fruit.
On 5 Sep 2003, Greg Stark wrote:
Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > Bruce Momjian wrote:
> >>> HINT: Perhaps you need to use 'createlang' to load the language into
> >>> the database, or you mistyped the language name.
>
> > Why not list out the languages we *do* know about, and tell them it's
> >
Hello
It would be very nice to create a way to log only bad queries, which's
resulted in an error. This way a higher loglevel wouldn't be necessary.
one other thing,
by sending a SIGHUP to the postmaster it reinits it's config files. Now
i've made some store functions in C, and it would be very n
-On [20030905 17:42], Rod Taylor ([EMAIL PROTECTED]) wrote:
>Is this beta 1 or beta 2? Beta 1 has a bug which may require more
>shared resources than what is available.
Sorry, beta 2. Should've made that clear.
--
Jeroen Ruigrok van der Werven / asmodai
PGP fingerprint: 2D92 980
Rod Taylor <[EMAIL PROTECTED]> writes:
>> did 7.4 raise the bar on SysV IPC? On my other two boxes I haven't
>> tweaked SysV IPC at all (semmni is at 10) and I get initdb.
> Is this beta 1 or beta 2? Beta 1 has a bug which may require more
> shared resources than what is available.
Actually the
"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> The thing that slows me down the most --- trips like FOSDEM. I am doing
> one every month or every other month. That takes 1/4 of each month.
> The threading discussion took 1/1000 of a month, but I do several
> hundred of those, so it fills up a mont
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> wrote:
>> I've found a number of infelicities in the hash index code that can't be
>> fixed without an on-disk format change.
> How can we avoid this kind of mess for the future ?
Build a time machine, go back fifteen
On Fri, 2003-09-05 at 11:29, Jeroen Ruigrok/asmodai wrote:
> -On [20030905 17:22], Jeroen Ruigrok/asmodai ([EMAIL PROTECTED]) wrote:
> >Well, on Itanium2 on FreeBSD 5.1 it compiles. I just need to get the
> >semaphores to a higher value in order to actually do an initdb.
>
>
-On [20030905 17:22], Jeroen Ruigrok/asmodai ([EMAIL PROTECTED]) wrote:
>Well, on Itanium2 on FreeBSD 5.1 it compiles. I just need to get the
>semaphores to a higher value in order to actually do an initdb.
Though,
did 7.4 raise the bar on SysV IPC? On my other two boxes I haven't
t
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> I've found a number of infelicities in the hash index code that can't be
> fixed without an on-disk format change. The biggest one is that the
> hashm_ntuples field in hash meta pages is only uint32, meaning that
> hash index space management will become co
Jan Wieck <[EMAIL PROTECTED]> writes:
> Redhat 7.1 says
> The file descriptor sockfd must refer to a socket. If the
> socket is of type SOCK_DGRAM then the serv_addr address is
> the address to which datagrams are sent by default, and
> the only address from w
-On [20030905 16:42], Rod Taylor ([EMAIL PROTECTED]) wrote:
>Download 7.4 beta 2 and run regression tests on those platforms. Report
>back any issues or successes. 7.4 Release candidates will come with a
>call for reports on platforms that pass the regression tests which are
>used to
Robert Creager wrote:
Once upon a time (Fri, 05 Sep 2003 03:16:54 -0400)
Andrew Dunstan <[EMAIL PROTECTED]> uttered something amazingly similar to:
Could we get the configure script to do it instead, since it too should
know about ip6 capability? (I guess then we'd have
pg_hba.conf.sample.in)
Vivek, you reported recently that increasing sort_mem and
checkpoint_segments increased performance. Can you run a test to see
how much of that improvement was just because of increasing
checkpoint_segments?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Shridhar Daithankar wrote:
> For heavily updated systems, you should have WAL buffers bit more. I don't know
> exact imact of that setting though. You could try 32/64/128. On the same note,
> if you are getting checkpoints too frequently, you can try increasing
> checkpoint segments. The logs wi
> I'm doing a research about DBMSs that run on new PC 64-bit processors, like
> Intel Itanium and AMD Opteron. I'd like that you would help me in some
> questions. First, does pgsql support this architecture? According to
> Administrator's
> Guide(http://www.postgresql.org/docs/7.3/static/supported
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The FAQ does have the example of using ORDER BY LIMIT 1 for MAX(). What
> we don't have a workaround for is COUNT(*). I think that will require
> some cached value that obeys MVCC rules of visibility.
Note that that only handles min()/max() for the w
Hello,
I'm a beginner here at the list, my name is Daniel Pellegrini, graduation
student from Brazil with no experience about pgsql. First of all I'd like to
say that I have tried other lists before, but I didn't get the answer, or
the complete answer.
I'm doing a research about DBMSs that run on
On Fri, 2003-09-05 at 09:52, Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > Bruce Momjian wrote:
> >>> HINT: Perhaps you need to use 'createlang' to load the language into
> >>> the database, or you mistyped the language name.
>
> > Why not list out the languages we *do* know ab
Christopher Browne <[EMAIL PROTECTED]> writes:
> Wouldn't this more or less be the same thing as having a trigger that
> does, upon each insert/delete "update pg_counts set count = count + 1
> where reltable = 45232;"? (... where 1 would be -1 for deletes, and where
> 45232 is the OID of the table
Jan Wieck wrote:
> Redhat 7.1 says
>
> The file descriptor sockfd must refer to a socket. If the
> socket is of type SOCK_DGRAM then the serv_addr address is
> the address to which datagrams are sent by default, and
> the only address from which datagrams are
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> OK, now we are getting somewhere. I see that this would work. It's a bit
> ugly, though - with this plan the sample file in both CVS and the
> installation won't necessarily be what actually get put in place.
Well, like I said, it's not real pretty.
Andrew Dunstan wrote:
> >Bruce and I were just discussing this on the phone. It seems we have
> >two basic approaches to problem #2. Either we hack the postmaster so
> >that it will swallow IPv6 addresses in pg_hba.conf even without any real
> >IPv6 support, or we make the default pg_hba.conf con
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Bruce Momjian wrote:
>>> HINT: Perhaps you need to use 'createlang' to load the language into
>>> the database, or you mistyped the language name.
> Why not list out the languages we *do* know about, and tell them it's
> not in the list? Or is that to
I get the following errors
gmake -C ecpglib all
gmake[4]: Entering directory
`/usr/local/postgres/pgsql/src/interfaces/ecpg/ecpg
lib'
../../../../src/backend/port/aix/mkldexport.sh libecpg.a > libecpg.exp
gcc -O2 -pipe -Wall -Wmissing-prototypes -Wmissing-declarations
-Wl,-bnoentry -
Wl,-H512 -W
Redhat 7.1 says
The file descriptor sockfd must refer to a socket. If the
socket is of type SOCK_DGRAM then the serv_addr address is
the address to which datagrams are sent by default, and
the only address from which datagrams are received. If
Looks like the tes
As long as you're sure.
"Bupp Phillips" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Will this have the native Windows port?
>
> ""Marc G. Fournier"" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> >
> >
> > On Tue, 2 Sep 2003, postgresql wrote:
> >
> > > Hi all
>
--On Thursday, September 04, 2003 16:17:48 -0300 "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
The full check out found them :-\
I dunno what was going on.
'k, as I said, for some reason the /projects/cvsroot itself wasn't being
updated properly either, so it might be related *shrug*
let me
NO!!! Don't remove SD and GD!!! They are useful.
I use them in several applications, primarily
for running aggregates.
What needs to be fixed is that the SD needs to be
initialized at the start of each statement.
Joe Conway just implemented this in Pl/R and
Tom Lane had an idea about it too.
See
1 - 100 of 106 matches
Mail list logo
