Re: [HACKERS] MERGE Specification

[EMAIL PROTECTED] (Decibel!) writes: > On Apr 22, 2008, at 1:17 PM, Gregory Stark wrote: >> "Simon Riggs" <[EMAIL PROTECTED]> writes: >> >>> As I've said elsewhere, we could have it lock each row, its just more >>> overhead if we do and not necessary at all for bulk data merging. >>> >>> I'll pres

Re: [HACKERS] Problem with server/utils/snapmgr.h

[EMAIL PROTECTED] (Alvaro Herrera) writes: > Chris Browne wrote: > >> If I use: >> AC_CHECK_HEADER(utils/snapmgr.h, HAVE_SNAPMGR=1) >> >> this turns out to fail. Apparently autoconf wants to compile the >> #include file to validate that it's an OK #i

[HACKERS] Problem with server/utils/snapmgr.h

There's a new #include file that it turns out we need for Slony-I to reference, namely include/server/utils/snapmgr.h I tried adding an autoconf rule to Slony-I to check for its existence (goal then is to do a suitable #define so that we can #ifdef the #include, so that we #include this only with

Re: [HACKERS] TODO, FAQs to Wiki?

[EMAIL PROTECTED] (Bruce Momjian) writes: > I am impressed at the state of the May wiki patch queue: > > http://wiki.postgresql.org/wiki/CommitFest:May > > It is even tracking the psql wrap patch I am working on now. Aside: I have made a few little changes that oughtn't be too controversial:

Re: [HACKERS] get rid of psql welcome message

[EMAIL PROTECTED] (Stephen Frost) writes: > * Peter Eisentraut ([EMAIL PROTECTED]) wrote: >> Around >> it >> was proposed to truncate the psql welcome screen. What do you think about >> that? > > I'd recommend an option in .psq

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> Would it be a terrible idea to... >> >> - Draw the indent code from NetBSD into src/tools/pgindent > > I am not real eager to become maintainers of our own indent fork, which

Re: [HACKERS] MERGE SQL Statement

[EMAIL PROTECTED] (Simon Riggs) writes: >> Should there be a new rule option? ie. ON MERGE rules ? > > Maybe, but not as part of this project. That seems to warrant a bit of elaboration... If we're running a MERGE, and it performs an INSERT or UPDATE of a particular tuple in(to) a particular ta

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Bruce Momjian) writes: > Chris Browne wrote: >> >> Would it be a terrible idea to... >> >> >> >> - Draw the indent code from NetBSD into src/tools/pgindent >> >> - Build it _in place_ inside the code tree (e.g. - don't

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Bruce Momjian) writes: > Chris Browne wrote: >> [EMAIL PROTECTED] (Bruce Momjian) writes: >> > Magnus Hagander wrote: >> >> > And I think adopting surrounding naming, commeting, coding conventions >> >> > should come naturally as i

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Bruce Momjian) writes: > Magnus Hagander wrote: >> > And I think adopting surrounding naming, commeting, coding conventions >> > should come naturally as it can aide in copy-pasting too :) >> >> I think pg_indent has to be made a lot more portable and easy to use >> before that

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Tom Lane) writes: > Magnus Hagander <[EMAIL PROTECTED]> writes: >> I think pg_indent has to be made a lot more portable and easy to use >> before that can happen :-) I've run it once or twice on linux machines, >> and it comes out with huge changes compared to what Bruce gets on

Re: [HACKERS] Commit fest status

[EMAIL PROTECTED] (Tom Lane) writes: > In short, I think it's time to declare our first commit fest done. Congratulations! As a pure observer in the matter, it has clearly been a somewhat painful process, which must be tempered by the consideration that what was being reviewed was pretty much a

Re: [HACKERS] Commit fest queue

[EMAIL PROTECTED] ("Joshua D. Drake") writes: > The base requirements for this process must be so simple, so easy, that > even if the person has never seen a C patch in his/her life they > understand what is trying to be achieved. Are you sure about that? I think that our concern is about the so

Re: [HACKERS] Feature freeze status

[EMAIL PROTECTED] (Heikki Linnakangas) writes: > Josh Berkus wrote: >> Maybe we should make the next commit-fest June 1 to give people some >> time off? And some time to improve the tools? > > I would rather do the commit fests often, to keep the patch queue and > the commit fests short. But if i

Re: [HACKERS] Transaction Snapshot Cloning

[EMAIL PROTECTED] (Bruce Momjian) writes: > Added to TODO: > > * Allow one transaction to see tuples using the snapshot of another > transaction > > This would assist multiple backends in working together. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php FYI, code for this

Re: [HACKERS] Sending queries directly

[EMAIL PROTECTED] ("Pedro Belmino") writes: > I am creating an agent that runs alongside the postgres written in > c++, I have a question: How send sql queries directly for the > database without going need to make any > connection? > What I > call function, which I use file? You don't do tha

Re: [HACKERS] Data Recovery feature

[EMAIL PROTECTED] ("Amit jain") writes: > What are the Data Recovery feature available in postgreSQL apart > from pg_restore and PITR. If my Database has corrupted its not > starting which feature i can use for Data Recovery ? Any help > willbe highly appreciated. The primary mechanism for datab

Re: [HACKERS] Transaction Snapshot Cloning

[EMAIL PROTECTED] (Simon Riggs) writes: > On Fri, 2008-01-11 at 20:39 +, Simon Riggs wrote: >> On Fri, 2008-01-11 at 15:05 -0500, Tom Lane wrote: >> Simon Riggs <[EMAIL PROTECTED]> writes: >> > > If we had a function >> > > replace_serializable_snapshot(master_xid, txid_snapshot) >> > > this

Re: [HACKERS] Dynamic Partitioning using Segment Visibility Maps

Ron Mayer <[EMAIL PROTECTED]> writes: > Chris Browne wrote: >> _On The Other Hand_, there will be attributes that are *NOT* set in a >> more-or-less chronological order, and Segment Exclusion will be pretty >> useless for these attributes. > > Really?I was h

Re: [HACKERS] Named vs Unnamed Partitions

[EMAIL PROTECTED] (Markus Schiltknecht) writes: > Simon Riggs wrote: >> With that in mind, can I clarify what you're thinking, please? > > Sure, I can try to clarify: > >> 2) the things you've been discussing are essential requirements of >> partitioning and we could never consider it complete unti

Re: [HACKERS] Dynamic Partitioning using Segment Visibility Maps

[EMAIL PROTECTED] (Simon Riggs) writes: > I think we have an opportunity to bypass the legacy-of-thought that > Oracle has left us and implement something more usable. This seems like a *very* good thing to me, from a couple of perspectives. 1. I think you're right on in terms of the issue of th

Re: [HACKERS] proposal, plpgsql, 8.4, for record in cursor

[EMAIL PROTECTED] (Peter Eisentraut) writes: > Am Montag, 26. November 2007 schrieb Tom Lane: >> "Pavel Stehule" <[EMAIL PROTECTED]> writes: >> > I propose new kind of FOR statement .. iteration over cursor, >> >> This seems useless and probably syntactically ambiguous. > > I think that is isomorph

Re: [HACKERS] psql show dbsize?

[EMAIL PROTECTED] (Tom Lane) writes: > Andrew Dunstan <[EMAIL PROTECTED]> writes: >> Perhaps both these considerations dictate providing another command or a >> special flavor of \l instead of just modifying it? > > I've seen no argument made why \l should print this info at all. Its interesting

Re: [HACKERS] Feature Freeze date for 8.4

[EMAIL PROTECTED] (Tom Lane) writes: > Simon Riggs <[EMAIL PROTECTED]> writes: >> I'd suggest we have multiple checkpoints during the cycle. Checkpoint is >> a "patch queue blitz" where we stop developing and reduce the queue to >> nothing. Perhaps a two-week period where everybody helps reduce the

Re: [HACKERS] Feature Freeze date for 8.4

[EMAIL PROTECTED] (Josh Berkus) writes: > Simon, > >> We can issue a provisional date. We could also say "at least 6 months >> after release date of 8.3". I'm sure there's other options too. > > I'm going to suggest 4 months after 8.3. 8.3 was supposed to be a *short* > release so that we could m

Re: [HACKERS] some points for FAQ

[EMAIL PROTECTED] (Alvaro Herrera) writes: > Pavel Stehule escribió: > >> p.s. can we create some general F.A.Q XML format and store FAQ there? >> >> WIP Proposal: >> >> >> >> >> >> ... >> we need some tags from html: > > There is a DocBook spec for FAQ lists. Actually a friend

Re: [HACKERS] 8.3 beta timing

[EMAIL PROTECTED] (Bruce Momjian) writes: > I think we need another week to get things ready for beta. I will have > the release notes done mid-week and hopefully we can close out all open > items by the end of the week. It's worth noting that Greg Smith has collected release note information int

Re: [HACKERS] Getting to 8.3 beta1

[EMAIL PROTECTED] (Teodor Sigaev) writes: >> * Draft release notes --- can't really ship a beta without these, >> else beta testers won't know what to test. Traditionally this has >> taken a fair amount of time, but I wonder whether we couldn't use >> http://developer.postgresql.org/index.php/What

Re: [HACKERS] terms for database replication: synchronous vs eager

[EMAIL PROTECTED] (Jan Wieck) writes: > On 9/7/2007 11:01 AM, Markus Schiltknecht wrote: >> None the less, Postgres-R is eager (or pessimistic?) in the sense >> that it replicates *before* committing, so as to avoid >> divergence. In [1] I've tried to make that distinction clear, and >> I'm current

Re: [HACKERS] tsearch2 patch status report

[EMAIL PROTECTED] (Tom Lane) writes: > The main thing that is lacking at the moment is documentation. The > stuff Bruce has been working on will be good introductory material, > but we've got basically zip in reference material. I'll do some work > on that over the next couple of days, but there'

[HACKERS] TOAST Threshold? Re: Status of 8.3 patches

[EMAIL PROTECTED] ("Joshua D. Drake") writes: > Alvaro Herrera wrote: >> Joshua D. Drake wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Heikki Linnakangas wrote: Joshua D. Drake wrote: > >>> I guess my point is, if the patch looks good and does not appear >>> to hurt anyt

Re: [HACKERS] Index Tuple Compression Approach?

[EMAIL PROTECTED] (Gregory Stark) writes: > "Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > >> Gregory Stark wrote: >>> "Heikki Linnakangas" <[EMAIL PROTECTED]> writes: >>> That general approach of storing a common part leading part just once is called prefix compression. Yeah, it he

Re: [HACKERS] Index Tuple Compression Approach?

[EMAIL PROTECTED] ("Dawid Kuroczko") writes: > On 8/14/07, Chris Browne <[EMAIL PROTECTED]> wrote: >> I recently had a chat with someone who was pretty intimate with Adabas >> for a number of years who's in the process of figuring things out >> about Postg

[HACKERS] Index Tuple Compression Approach?

I recently had a chat with someone who was pretty intimate with Adabas for a number of years who's in the process of figuring things out about PostgreSQL. We poked at bits of the respective implementations, seeing some similarities and differences. He pointed out one aspect of index handling that

Re: [HACKERS] RIP: Buildfarm member Baiji ??

a snapshot for the last few days... 1 extinct, 1 in coma -> not going too well for dolphins these days ;) Bye, Chris. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [HACKERS] [GENERAL] 8.2.4 signal 11 with large transaction

e not worth that much, but as a DBA, I would really like for you to print at least some of the string causing the abend. This would greatly assist in the tracing of the offending query. Chris

Re: [HACKERS] Future of krb5 authentication

[EMAIL PROTECTED] (Peter Eisentraut) writes: > Am Mittwoch, 18. Juli 2007 13:21 schrieb Magnus Hagander: >> The main reasons would be to have less code to maintain, > > I don't think the krb5 support has needed all that much maintenance in the > last few years. > >> and to make life >> easier for

Re: [HACKERS] compiler warnings on the buildfarm

[EMAIL PROTECTED] (Stefan Kaltenbrunner) writes: > Tom Lane wrote: > [...] >>> animal: clownfish warnings: 12 >>> "dynloader.c", line 4: warning: empty translation unit >>> "postgres.c", line 3758: warning: loop not entered at top >> >> The first of these is not a bug, the second seems

Re: [HACKERS] 2PC-induced lockup

[EMAIL PROTECTED] writes: > On Wed, Jul 11, 2007 at 12:38:09AM -0400, Tom Lane wrote: >> [EMAIL PROTECTED] writes: > [...] >> > It might make sense then to clear the pg_twophase directory on DB >> > startup. >> >> I fear you have 100% misunderstood the point. The *only* >> reason for that featu

[HACKERS] no cascade triggers?

ns for our user? He has a somewhat large number of triggers that do the alter table trick - working around it by means of some context-based logic would be a lot of work... Bye :) Chris. ---(end of broadcast)--- TIP 4: Have you searche

Re: [HACKERS] PG-MQ?

[EMAIL PROTECTED] ("Marko Kreen") writes: > To Chris: you should like PgQ, its just stored procs in database, > plus it's basically just generalized Slony-I, with some optimizations, > so should be familiar territory ;) Looks interesting... Random ideas - i

Re: [HACKERS] PG-MQ?

[EMAIL PROTECTED] (Steve Atkins) writes: >> Is there any existing work out there on this? Or should I maybe be >> looking at prototyping something? > > The skype tools have some sort of decent-looking publish/subscribe > thing, PgQ, then they layer their replication on top of. It's multi > consume

[HACKERS] PG-MQ?

I'm seeing some applications where it appears that there would be value in introducing asynchronous messaging, ala "message queueing." The "granddaddy" of message queuing systems is IBM's MQ-Series, and I don't see particular value in replicating its fu

Re: [HACKERS] TOAST usage setting

[EMAIL PROTECTED] (Bruce Momjian) writes: > The results are here: > > http://momjian.us/expire/TOAST/ I'll take a look and see if there's anything further it makes sense for me to try testing. Thanks for following up so quickly; what with the cold I have had, I haven't yet gotten back to th

Re: [HACKERS] Not ready for 8.3

[EMAIL PROTECTED] (Aidan Van Dyk) writes: > * Tatsuo Ishii <[EMAIL PROTECTED]> [070516 07:23]: > >> Maybe. However I think "subject-sequence" has some advantages over >> Message-Id: >> >> - Easy to identify. Message-Id may not appear on some MUA with default >> setting >> >> - More handy than

Re: [HACKERS] Not ready for 8.3

[EMAIL PROTECTED] (Josh Berkus) writes: > Bruce, > > Realistically I just don't see getting everything in the ToDo patch > list in; my vote is that we start deferring stuff for 8.4 if it > doesn't have a reviewer, except for items which were submitted early > in the cycle (and to whom it would be u

Re: [pgsql-www] [HACKERS] Feature freeze progress report

project on some ftp server if anyone was interested in preserving that ifnormation for posterity. It would not be difficult for me to get a list of email addresses and project names of those admins on gborg. Chris Ryan --- "Marc G. Fournier" <[EMAIL PROTECTED]> wrote: >

Re: [HACKERS] Feature freeze progress report

[EMAIL PROTECTED] (Andrew Dunstan) writes: > Tom Lane wrote: >> So in a roundabout way we come back >> to the idea that we need a bug tracker (NOT a patch tracker), plus >> people putting in the effort to make sure it stays a valid source >> of up-to-date info. Without the latter it won't really b

Re: [HACKERS] Feature freeze progress report

[EMAIL PROTECTED] (Marc Munro) writes: > On Mon, 2007-30-04 at 08:56 -0300, Heikki Linnakangaspgsql wrote: >> Date: Mon, 30 Apr 2007 09:18:36 +0100 >> From: Heikki Linnakangas <[EMAIL PROTECTED]> >> To: Tom Lane <[EMAIL PROTECTED]> >> Cc: Dave Page <[EMAIL PROTECTED]>, Simon Riggs >> <[EMAIL PROTEC

Re: [HACKERS] Modifying TOAST thresholds

[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> [EMAIL PROTECTED] (Bruce Momjian) writes: >>> I have seen no one do peroformance testing of this, so it seems it >>> will have to wait for 8.4. > >> I didn't have time.

Re: [HACKERS] Modifying TOAST thresholds

[EMAIL PROTECTED] (Bruce Momjian) writes: > I have seen no one do peroformance testing of this, so it seems it > will have to wait for 8.4. I didn't have time... I'll see if I can find a decent place to document how to tweak the threshold, as that seems like it could be worth doing in cases where

Re: [HACKERS] Hacking on PostgreSQL via GIT

[EMAIL PROTECTED] (Aidan Van Dyk) writes: > I've "diffed" a CVS checkout and a git checkout, and the are *almost* > identical. Almost, because it seems like my git repository currently has 3 > files that a cvs checkout doesn't: > backend/parser/gram.c |12088 ++

Re: [HACKERS] Hacking on PostgreSQL via GIT

[EMAIL PROTECTED] ("Florian G. Pflug") writes: > Martin Langhoff wrote: >> Hi Florian, >> I am right now running an rsync of the Pg CVS repo to my work >> machine to >> get a git import underway. I'm rather keen on seeing your cool PITR Pg >> project go well and I have some git+cvs fu I can apply h

Re: [HACKERS] What X86/X64 OS's do we need coverage for?

ler@lerctr.org ("Larry Rosenman") writes: > I might use that as the base then, since the hardware finishes getting here > tomorrow. > > My question still stands on what OS's we need coverage for. I've got Debian testing/unstable covered. I'm not sure we have Novell/SuSE covered... -- output = ("

Re: [HACKERS] Modifying TOAST thresholds

[EMAIL PROTECTED] (Tom Lane) writes: > Bruce Momjian <[EMAIL PROTECTED]> writes: >> The big question is whether this is for 8.3 or 8.4. > > What I would definitely like to see for 8.3 is some performance testing > done to determine whether we ought to change the current defaults. > (Both TOAST_TUPL

Re: [HACKERS] Modifying TOAST thresholds

[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> [EMAIL PROTECTED] (Tom Lane) writes: >>> ... tuning the TOAST parameters seems like >>> something we understand well enough already, we just need to put some >>> cycles int

Re: [HACKERS] Modifying TOAST thresholds

[EMAIL PROTECTED] (Tom Lane) writes: > "Simon Riggs" <[EMAIL PROTECTED]> writes: >> Well it certainly seems worth separating them. It does seem possible >> that recursive toasting effected some of the earlier results we looked >> at. > >> Would you like me to do this, or will you? > > I'm willing t

Re: [HACKERS] TOASTing smaller things

[EMAIL PROTECTED] ("Luke Lonergan") writes: > Andreas, > > On 3/22/07 9:40 AM, "Andreas Pflug" <[EMAIL PROTECTED]> wrote: > >> Wouldn't it be enough to enable having the toast table on a different >> table space? > > Yes, but the ultimate goal would allow the allocation of a storage mechanism > tha

Re: [HACKERS] TOASTing smaller things

[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> #define TOAST_DENOMINATOR 17 >>/* Use this as the divisor; current default behaviour falls from >> TOAST_DENOMINATOR = 4 */ > >> #define TOAST_TUPLE_THRESHOLD^I\ >&g

[HACKERS] TOASTing smaller things

In some of our applications, we have cases where it would be very nice if we could activate TOAST at some sort of lower threshold than the usual 2K that is true now. Let me note the current code that controls the threshold: /* * These symbols control toaster activation. If a tuple is larger tha

[HACKERS] Question about the TODO, numerics, and division

missing something? Best Wishes, Chris Travers begin:vcard fn:Chris Travers n:Travers;Chris email;internet:[EMAIL PROTECTED] tel;work:509-888-0220 tel;cell:509-630-7794 x-mozilla-html:FALSE version:2.1 end:vcard ---(end of broadcast)--- TIP 4:

Re: [HACKERS] Auto creation of Partitions

[EMAIL PROTECTED] (Peter Eisentraut) writes: > NikhilS wrote: >> iv) Based on the PRIMARY, UNIQUE, REFERENCES information specified, >> pass it on to the children tables. > > How will you maintain a primary key in such a table, considering that > indexes can't span multiple tables? On the one han

Re: [HACKERS] PostgreSQL - 'SKYLINE OF' clause added!

[EMAIL PROTECTED] (Jim Nasby) writes: > FWIW, this sounds like a subset of the Query By Example stuff that > someone is working on. I don't have a URL handy since I'm on a plane, > but I think google can find it. The pgFoundry project is here... http://pgfoundry.org/projects/qbe And yes, indee

Re: [HACKERS] [Monotone-devel] Re: SCMS question

[EMAIL PROTECTED] (Richard Levitte - VMS Whacker) writes: > In message <[EMAIL PROTECTED]> on Thu, 22 Feb 2007 17:38:26 +0100, Markus > Schiltknecht <[EMAIL PROTECTED]> said: > > markus> > So far, I'm getting the sense that there are a lot of > markus> > opinions on what replacement system to use,

Re: [HACKERS] [Monotone-devel] Re: SCMS question

[EMAIL PROTECTED] (Andrew Dunstan) writes: > Tom has pointed out, our biggest pain point is > the occasional wish to move things across directories. That's the biggest pain that people are normally aware of. There are things that people don't even bother to try to do with CVS because they are so

Re: [HACKERS] autovacuum next steps

[EMAIL PROTECTED] (Alvaro Herrera) writes: > When there is a single worker processing a database, it does not recheck > pgstat data after each table. This is to prevent a high-update-rate > table from starving the vacuuming of other databases. This case is important; I don't think that having mul

Re: [HACKERS] Data archiving/warehousing idea

G'day Gavin, In maillist.postgres.dev, you wrote: > On Thu, 1 Feb 2007, Chris Dunlop wrote: >> The main idea is that, there might be space utilisation and >> performance advantages if postgres had "hard" read-only >> tables, i.e. tables which were guaranteed

[HACKERS] Data archiving/warehousing idea

able to the "read only" format, rewrite the indexes for maximum packing and collect stats for the planner etc. Thoughts? Brickbats? Cheers, Chris. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [HACKERS] Proposal: Snapshot cloning

[EMAIL PROTECTED] (Gregory Stark) writes: > "Jan Wieck" <[EMAIL PROTECTED]> writes: > >> backend1: select publish_snapshot(); -- will block >> >> backend2: start transaction; >> backend2: set transaction isolation level serializable; >> backend2: select clone_snapshot(); -- will unb

Re: [HACKERS] Proposal: Change of pg_trigger.tg_enabled and adding

[EMAIL PROTECTED] (Markus Schiltknecht) writes: > Nice proposal. I'd support that enhancement and could make use of such > triggers in Postgres-R as well, at least to provide these triggers to > the user. > > Jan Wieck wrote: >> Good question. I don't know. I'd rather error on the safe side and >>

Re: [HACKERS] [COMMITTERS] pgsql: Stamp major release 8.3.0,

4.0, and likely 3.9. Bye :) Chris. PS: OpenBSD 4.0 current is fixed, but I was reluctant to update to current... ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

Re: [HACKERS] [COMMITTERS] pgsql: Stamp major release 8.3.0,

then I'm going to upgrade her only when 4.1-stable comes out (in May). (i keep having this idea that if we all run current/unstable versions of our OSes we might overlook other issues ...) Bye, Chris. ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate

Re: [HACKERS] TODO: GNU TLS

[EMAIL PROTECTED] ("Joshua D. Drake") writes: >> The reason I wanted to use PGP is that I already have a PGP key. X.509 >> certificates are far too complicated (a certificate authority is a >> useless extra step in my case). > > Complete side note but one feature that I brought up to my team a > po

Re: [HACKERS] Deadline-Based Vacuum Delay

[EMAIL PROTECTED] ("Jaime Casanova") writes: > On 12/28/06, Tom Lane <[EMAIL PROTECTED]> wrote: >> Galy Lee <[EMAIL PROTECTED]> writes: >> > So I am thinking another way to perform vacuum. For example vacuum can >> > be refined in a maintenance time frame like "VACUUM IN 6 HOURS", and >> > then vac

Re: [HACKERS] Stats Collector Oddity

[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> We're getting a bit of an anomaly relating to pg_stat_activity... >> ... >> That PID has been dead for several days, but this connection is marked >> as being open, still, afte

Re: [HACKERS] Release 8.2.0 done, 8.3 development starts

[EMAIL PROTECTED] (Kaare Rasmussen) writes: > I'm not sure, but as far as I remember, it will be a short release cycle for > 8.3 in order to finish some big items that couldn't be ready in time for 8.2. > > But which items are more or less expected for 8.3? I recall > - Hierarchical Queries > -

[HACKERS] Stats Collector Oddity

We're getting a bit of an anomaly relating to pg_stat_activity... oxrstld=# SELECT * from pg_stat_activity where current_query <> ''; datid| datname | procpid | usesysid | usename | current_query | query_start +-+-+--+-+---

Re: [HACKERS] development environment of postgres

[EMAIL PROTECTED] (dakotali kasap) writes: > I want to ask, which development environment should I use to add new > features to postgresql. Is Eclipse CDT (C/C++ Development Tool) > suitable for this, or are you using another environment, or just > using pico, vi, etc.? I can't speak for you. I f

Re: [HACKERS] error compiling 8.2 in debian sarge

--enable-debug--enable-cassert --enable-depend > Again, no problem here. Some version infos are below. Bye, Chris. [EMAIL PROTECTED]:~$ uname -a Linux guest05 2.4.27-3-386 #1 Mon May 29 23:50:41 UTC 2006 i686 GNU/Linux [EMAIL PROTECTED]:~$ gcc --version gcc (GCC) 3.3.5 (Debian 1:3.3.5-13

Re: [HACKERS] error compiling 8.2 in debian sarge

> i'm using debian sarge and when trying to compile 8.2beta3 got this fail... Just checked: no problems here on a stock 3.1. What ./configure switches did you use? Bye, Chris. ---(end of broadcast)--- TIP 3: Have you checked our exten

Re: [HACKERS] Deadlock with pg_dump?

t_activity, perhaps)? I guess the conflicting backend would currently be waiting for a lock, so its current query (before releasing the lock) is the one we want. Thanks! - Chris ---(end of broadcast)--- TIP 3: Have you checked our ext

Re: [HACKERS] Deadlock with pg_dump?

ses hold, and what queries they were running when the deadlock occurred? Is that easily done, without turning on logging for *all* statements? Thanks! - Chris ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ?

[HACKERS] Deadlock with pg_dump?

pgbench tables) and pg_dump in tight loops in two concurrent shell scripts, but no deadlock. Any ideas on how to track this down? Under what conditions does a process acquire a ShareLock on another transaction? Thanks! - Chris Tab

Re: [HACKERS] Syntax bug? Group by?

e that exactly match expressions in the WHERE clause. Thanks! - Chris ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [HACKERS] OT: Is there a LinkedIn group for Postgresql?

[EMAIL PROTECTED] (Tzahi Fadida) writes: > Hi, > Is there a LinkedIn group for Postgresql/Hackers list. > If there is, how can i join? The usual way LinkedIn works is that if there are people you know that do PostgreSQL work, they may link to others doing the same. You should probably see about l

Re: [HACKERS] [PATCHES] Use non-deprecated APIs for dynloader/darwin.c

rviceDiscovery.h if not (which will be the case for 10.2). Thanks! - Chris ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

[HACKERS] libreadline only used with psql?

er, pg_ctl, pg_dump, pg_restore, etc) won't require it. This request would be accompanied by a patch, but I wanted to ask about the feasibility of a PSQL_LIBS variable before going down that road. Thanks! - Chris ---(end of broadcast)---

Re: [HACKERS] Query Failed, out of memory

See FETCH_COUNT in http://developer.postgresql.org/pgdocs/postgres/app-psql.html Bye, Chris. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [HACKERS] PostgreSQL HA questions

here are several strategies for this. My > colleague Chris Browne seems really to like this kind of > functionality, and has discussed it more than once on the -general > list. I think you can find his detailed outlines of how to do this > sort of thing by searching for "rotor tab

Re: [HACKERS] Please to technical check of upcoming release

ll see "Theo Scholossenagle" there. I realize the quote is not ready anyway, but why not fix the name in the mean time: it should be "Theo Schlossnagle". Bye, Chris. ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [HACKERS] Release Notes: Major Changes in 8.2

[EMAIL PROTECTED] (Bruce Momjian) writes: > Josh Berkus wrote: >> Bruce, >> >> What happened to PL/pgSQL debugging? Did it die? > > The debuggers is going to be on pgfoundry, if it isn't there already. > The idea is that it would be loadable for 8.2, work out all the bugs, > and perhaps included

Re: [HACKERS] Mid cycle release?

[EMAIL PROTECTED] ("Joshua D. Drake") writes: > Leaving autovacuum on will cement the idea that it *should* be on and > IMHO it shouldn't without specific and careful planning. For the "completely naive user," it seems to me that it *should* be on, as that will diminish the number of questions tha

Re: [HACKERS] AIX shared libraries

[EMAIL PROTECTED] ("Rocco Altier") writes: >> Tom Lane wrote: >> > Is it >> > possible that the rules have changed across AIX versions, >> > and that the code in there now is needful for older versions? >> >> I don't think that this behaviour has changed. I remember it from >> AIX 4.3.2. >> > AI

Re: [HACKERS] Foreign keys

etting you insert 1000 records, then, at the end say: "hah, all is rolled back becauase the 2nd record was invalid". PG justly throws the exception immediately to let you know it's futile inserting 998 more records. I don't see a problem here. Bye, Chris. -- Chris Mair http

Re: [HACKERS] New Linux Filesystem: NILFS

[EMAIL PROTECTED] (Jeff Davis) writes: > On Wed, 2006-09-06 at 22:12 -0400, Christopher Browne wrote: > >> > Can you elaborate a little? Which filesystems have been problematic? >> > Which filesystems are you more confident in? >> >> Well, more or less *all* of them, on AMD-64/Linux. >> >> The "p

Re: [HACKERS] New Linux Filesystem: NILFS

[EMAIL PROTECTED] (Jeff Davis) writes: > On Tue, 2006-09-05 at 23:28 -0400, [EMAIL PROTECTED] wrote: >> On Tue, Sep 05, 2006 at 05:54:50PM -0700, Jeff Davis wrote: >> > On Tue, 2006-09-05 at 18:24 -0400, Chris Browne wrote: >> > > Recently seen in ACM Operating Sys

Re: [HACKERS] Ding-dong, contrib is dead ...

josh@agliodbs.com (Josh Berkus) writes: > Overall, though, I think we should really wait until 8.3 for core merge and > API improvements. Wasn't Tom just complaining about last-minute features, > and not enough code reviewers? He may have worked through enough of the backlog that he's ready to

Re: [HACKERS] Open items for 8.2

[EMAIL PROTECTED] (Bruce Momjian) writes: > Here are the open items for 8.2: > > http://momjian.postgresql.org/cgi-bin/pgopenitems > > This list will be continually updated until we release 8.2. I've got suggested patches for my item (e.g. - --with-openssl causing contrib stuff to break on A

[HACKERS] New Linux Filesystem: NILFS

Recently seen in ACM Operating Systems Review (this is the first time I've found as many as 1 interesting article in it in a while, and there were 3 things I found worthwhile...): NTT (of the recent "NTT Power Hour") have created a new filesystem: NILFS is a log-struc

Re: [HACKERS] ECPG regression failures on OpenBSD

: http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=guppy&dt=2006-09-05% 2010:02:05 Michael, if you want shell access to guppy, just contact me privately. Warning: guppy too, is somewhat dated (1:10 hours for the make step) :/ Bye, Chris. -- Chris Mair http://www.1006.org -

<    1   2   3   4   5   6   >