Greg Patnude [EMAIL PROTECTED] writes:
It would be really sweet in postgreSQL if we could apply the
equivalent of a printf(columnname) to the table definition -- MS
Access has what they call an input mask and it comes in really
handy -- however -- I havent used Access for anthing serious for
I recently had the 'joy' of needing to compile a copy of 7.1, to
support a fairly crusty application where we'd have to do more testing
than we can justify in order to upgrade to some (vastly) newer
generation.
Ran into a couple of things worth mentioning:
1. Had a whole lot of gory problems
[EMAIL PROTECTED] (Andrew Dunstan) writes:
Karel Zak wrote:
Hi,
in TODO is item: * Allow dump/load of CSV format. I don't think
it's clean idea. Why CSV and why not something other? :-)
A why not allow to users full control of the format by they own
function. It means something like:
[EMAIL PROTECTED] (Marc G. Fournier) writes:
On Thu, 1 Apr 2004, Christopher Kings-Lynne wrote:
Is your timeline based on the assumption of doing all the work
yourself? If so, how about farming out some of it? I'd be
willing to contribute some effort to PITR. (It's been made clear
to
We have encountered a pretty oddball situation involving an unknown type.
mydb=# select version();
version
[EMAIL PROTECTED] (Jim C. Nasby) writes:
I would still argue that if any language should be installed by
default it should be plpgsql and not java. As I mentioned, everyone
using a database already knows SQL; not nearly as many know java.
A vital factor is indeed that pl/pgsql does not require
[EMAIL PROTECTED] (Dave Cramer) writes:
Pl/J is a java procedural language for postgres. We are looking for
alpha testers to help us find bugs, and get feedback.
The project can be found at
http://plj.codehaus.org/
Bugs can be reported at
I was wanting to check out what was up with timezone handling with the
latest changes that were committed, as there had been some biting on
AIX.
To wit, notice the default time zone on one of our AIX boxes:
bash-2.05a$ date
Tue May 18 21:47:37 GDT 2004
bash-2.05a$ echo $TZ
CUT0GDT
bash-2.05a$
Santo Quartarone [EMAIL PROTECTED] writes:
What's the safest email browser?
less is pretty safe, more or less ;-).
You didn't specify what sort of platform you wanted to use; the
choices vary, considerably, between platforms.
--
(format nil [EMAIL PROTECTED] cbbrowne cbbrowne.com)
I just had a thought; was looking at a script where I'd rather invoke
using psql than using a Perl module (since Pg/DBD that might very well
not be available on AIX, HP/UX, Solaris, or such).
What would be very nice would be for there to be a psql command option
that would accept a DSN as opposed
[EMAIL PROTECTED] (chinni) writes:
Postgres-R is a multi server (write anywhere) replication tool
which is possibly important for any enterprise if they want to shift
to postgres.
Did you guys debate on merging it.
I seem to recall there being a licensing issue; Postgres-R uses the
[EMAIL PROTECTED] (Rod Taylor) writes:
On Sun, 2004-09-05 at 13:43, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
collect2: ld returned 254 exit status
That's a fairly unhelpful error message, isn't it?
I'm thinking that this may be due to having added the timezone
library to the
We have discovered an interesting locking scenario with Slony-I that
is pointing to a use for the ability to exclude certain schemas from
pg_dump.
The situation is that when a full pg_dump kicks off, a Slony-I
create sync event, which expects to LOCK slony_schema.sl_event;,
is blocked from
[EMAIL PROTECTED] (Josh Berkus) writes:
Lots of people have talked about it but I don't know anyone coding it.
I would love to have bitmap indexes in Postgres, as would a lot of other
community members. However, they are far from trivial to code. Are you
offering to help?
I'm curious
[EMAIL PROTECTED] (Yann Michel) writes:
On Fri, Oct 08, 2004 at 10:09:18AM +0100, Dave Page wrote:
I think what Reini was asking was why do you think you need bitmap
indexes as opposed to any existing type?
due to I'm developing a datawarehousing application we have lots of
fact-data in our
[EMAIL PROTECTED] (Bruce Momjian) writes:
Have you tried using cc_r for that compile line? Does that help?
Alas, that is not an option available.
cc_r is specific to the AIX xlc compiler; we're using GCC, and xlc
is not available to us.
bash-2.05a$ gcc -v
Reading specs from
[EMAIL PROTECTED] (Darcy Buskermolen) writes:
On September 30, 2004 05:55 pm, Bruce Momjian wrote:
To me it looks like all you need to do is add -pthreads or maybe
-lpthreads depending on exact system to your compile line..
-lpthreads does the trick, indeed. (-lpthread also does the job,
The Slony-I team is proud to present the 1.0.4 release of the most
advanced replication solution for the most advanced Open Source
Database in the world.
The release tarball is available for download
http://developer.postgresql.org/~wieck/slony1/download/slony1-1.0.4.tar.gz
There are a
Christopher Browne [EMAIL PROTECTED] writes:
There are essentially four choices:
Aside:
I suppose there are as many possible choices as there are bytecode
compiled systems out there. One could consider Icon, CLISP, Python,
PHP, OCAML, CMU/CL, all of which have bytecode compilers.
But none of
Just ran into a fascinating edge case. One of our folks was building
a stored function, and ran into an odd error when trying to COPY to
stdout.
Here's a characteristic example:
create or replace function build_table (integer) returns integer as '
begin
execute ''copy foo to stdout;'';
[EMAIL PROTECTED] (Alvaro Herrera) writes:
On Thu, Aug 25, 2005 at 02:45:02PM -0700, Joshua D. Drake wrote:
If y'all would like, I can eliminate the anti-virus/anti-spam checks and
just let it all go through though ... *evil grin*
Would not bother me in the least. I have protective
[EMAIL PROTECTED] (Alvaro Herrera) writes:
Or, slightly different, what are people's most wanted features?
- Vacuum Space Map - Maintain a map of recently-expired rows
This allows vacuum to target specific pages for possible free
space without requiring a sequential scan.
- Deferrable
[EMAIL PROTECTED] (David Parker) writes:
The slony log trigger saves execution plans, so any given connection
that has been used with a slony schema installed will have cached OIDs
referring to the sl_log_1 table. When you drop the schema, those OIDs
obviously go away. When you re-create the
[EMAIL PROTECTED] (Alvaro Herrera) writes:
On Tue, Aug 30, 2005 at 12:45:18PM -0400, Chris Browne wrote:
[EMAIL PROTECTED] (David Parker) writes:
The slony log trigger saves execution plans, so any given
connection that has been used with a slony schema installed will
have cached OIDs
[EMAIL PROTECTED] (huaxin zhang) writes:
not sure where to put this.
I run two queries:
1. select count(*) from table where indexed_column10;
2. select * from table where indexed_column10;
the indexed column is not clustered at all. I saw from the trace
that both query runs through
[EMAIL PROTECTED] (Joshua D. Drake) writes:
Hans-Jürgen Schönig wrote:
no because a new is not a heap ...
Why not use a function with a temporary table?
That way you can pass a table parameter that
is the temporary table with a select statement
that you can populate the temp table with.
[EMAIL PROTECTED] (Steve Atkins) writes:
We started our upgrade from 7.2 to 7.4 about 20 months ago and finished it
about 10 months ago, skipping 7.3 entirely.
We did similar; there was only one system deployed in a timeframe
where 7.3 was relevant, and the big systems skipped over 7.3 much as
[EMAIL PROTECTED] (Marc G. Fournier) writes:
On Mon, 26 Sep 2005, Josh Berkus wrote:
Tom,
Or, as you say, we could take the viewpoint that there are commercial
companies willing to take on the burden of supporting back releases, and
the development community ought not spend its limited
[EMAIL PROTECTED] (Hannu Krosing) writes:
It also seems that Slony can be modified to not use LISTEN/NOTIFY in
high load situations (akin to high performance network cards, which
switch from interrupt driven mode to polling mode if number of packets
per second reaches certain thresolds).
[EMAIL PROTECTED] (Andreas Pflug) writes:
Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
So postmaster doesn't clean up pg_listener,
It never has. If you're complaining about this patch
http://archives.postgresql.org/pgsql-committers/2005-10/msg00073.php
you ought to say so,
[EMAIL PROTECTED] (Tom Lane) writes:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
hmm well -HEAD(and 8.0.4 too!) is broken on AIX 5.3ML3:
http://archives.postgresql.org/pgsql-hackers/2005-10/msg01053.php
[ shrug... ] The reports of this problem have not given enough
information to fix it,
[EMAIL PROTECTED] (Jim C. Nasby) writes:
On Tue, Nov 01, 2005 at 11:23:55AM -0300, Alvaro Herrera wrote:
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
AFAIK they're not using subtransactions at all, but I'll check.
Well, yeah, they are ... else you'd never have seen this
[EMAIL PROTECTED] (Jim C. Nasby) writes:
AFAIK they're not using subtransactions at all, but I'll check.
Are they perchance using pl/PerlNG?
We discovered a problem with Slony-I's handling of subtransactions
which was exposed by pl/PerlNG, which evidently wraps its SPI calls
inside
[EMAIL PROTECTED] (Alvaro Herrera) writes:
Chris Browne wrote:
[EMAIL PROTECTED] (Jim C. Nasby) writes:
On Tue, Nov 01, 2005 at 11:23:55AM -0300, Alvaro Herrera wrote:
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
AFAIK they're not using subtransactions at all, but I'll
[EMAIL PROTECTED] (Tom Lane) writes:
The 8.1 supported-platforms list is looking pretty good, I think -- we
don't have updates for every single combination of OS and hardware,
but we have updates for every OS and at least one instance of all
supported CPU types.
Not to pester overly...
AIX
[EMAIL PROTECTED] (Gavin Sherry) writes:
Hi,
On Tue, 14 Nov 2005 [EMAIL PROTECTED] wrote:
Gavin Sherry:
Grouping sets
Recursive queries
The recursive queries is a long-awaited feature. Does the fact that
the feature is listed for Gavin Sherry mean that Gavin is
[EMAIL PROTECTED] (Russell Smith) writes:
Because it's not the hub of PostgreSQL development. I think it will
be difficult to build a culture of This is the place to be unless
we actually kill gborg totally. Currently there are still projects
there, I'm personally never sure where to look
[EMAIL PROTECTED] (Stephen Frost) writes:
* Tom Lane ([EMAIL PROTECTED]) wrote:
I think most of the real advantages of bug trackers that have been
mentioned in this thread have to do with history and searchability.
We have the raw info for that, in the pgsql-bugs and
pgsql-commmitters mail
[EMAIL PROTECTED] (Gustavo Tonini) writes:
But, wouldn't the performance be better? And wouldn't asynchronous
messages be better processed?
Why do you think performance would be materially affected by this?
The MAJOR performance bottleneck is normally the slow network
connection between
Lukas Smith [EMAIL PROTECTED] writes:
Bruce Momjian wrote:
* Flush cached query plans when the dependent objects change,
when the cardinality of parameters changes dramatically, or
when new ANALYZE statistics are available
Wouldn't it also make sense to flush a cached
[EMAIL PROTECTED] writes:
On Thu, Jan 19, 2006 at 09:37:12AM -0500, Pollard, Mike wrote:
Martijn van Oosterhout wrote:
Please provides natural keys for any of the following:
- A Person
- A phone call: (from,to,date,time,duration) is not enough
- A physical address
- A phone line:
matthew@zeut.net (Matthew T. O'Connor) writes:
Legit concern. However one of the things that autovacuum is supposed to
do is not vacuum tables that don't need it. This can result in an overal
reduction in vacuum overhead. In addition, if you see that autovacuum is
firing off vacuum commands
[EMAIL PROTECTED] (Alvaro Herrera) writes:
Chris Browne wrote:
It strikes me as a slick idea for autovacuum to take on that
behaviour. If the daily backup runs for 2h, then it is quite futile
to bother vacuuming a table multiple times during that 2h period when
none of the tuples obsoleted
[EMAIL PROTECTED] (Tom Lane) writes:
Alvaro Herrera [EMAIL PROTECTED] writes:
Hmm, yeah, sounds useful. There's one implementation issue to notice
however, and it's that the autovacuum process dies and restarts for each
iteration, so there's no way for it to remember previous state unless
[EMAIL PROTECTED] (Mark Woodward) writes:
The port aspect is troubling, it isn't really self
documenting. The application isn't psql, the applications are custom
code written in PHP and C/C++.
Nonsense. See /etc/services
Using the /etc/hosts file or DNS to maintain host locations for is
a
kleptog@svana.org (Martijn van Oosterhout) writes:
On Sat, Feb 04, 2006 at 01:54:52AM +0100, Peter Eisentraut wrote:
I took a first swing at this and rearranged some of these calls.
ld -- On AIX at least this seems to be some magic library but doesn't
have an obvious testable symbol.
[EMAIL PROTECTED] (Robert Treat) writes:
On Tuesday 14 February 2006 16:00, Martijn van Oosterhout wrote:
I would like to suggest that we increase substantially the FAQ entries
relating to patch submission. By we, I actually mean please could the
committers sit down and agree some
[EMAIL PROTECTED] (Greg Stark) writes:
Christopher Browne [EMAIL PROTECTED] writes:
Letter of Invitation for Countries Whose Citizens Require a
Temporary Resident Visa to Enter Canada
I missed that this was happening up here in Canada. How exclusive is
the guest list for this? Like, are
[EMAIL PROTECTED] (Markus Bertheau) writes:
2006/3/17, Bruce Momjian pgman@candle.pha.pa.us:
Peter Eisentraut wrote:
Bruce Momjian wrote:
The psql manual pages for 8.1 now has:
\set HISTFILE ~/.psql_history- :DBNAME
Any reason psql doesn't do this by default? It is
[EMAIL PROTECTED] (Dhanaraj M - Sun Microsystems) writes:
Hi all,
I have recented joined and working on postgres. I fixed a bug that I
saw in the mailing list. I ran the regression test that is available
in postgres. It was successful and now I need the following details..
1) Test suits
[EMAIL PROTECTED] (Tom Lane) writes:
If your pg_hba.conf looks like
hostall all 0.0.0.0/32 md5
there's not much call to update it dynamically ...
There's one case, where .pgpass got hosed, and you didn't have a
backup of it, and need to assign new passwords...
I once
[EMAIL PROTECTED] (Andrew Dunstan) writes:
We don't have the luxury of being able just to throw out old stuff
because we think it might be neater to do it another way. The current
rules for HBA are order dependent. The issue raised as I understood it
was not to invent a new scheme but to be
[EMAIL PROTECTED] (Gevik Babakhani) writes:
This may be a dumb question but please bear a moment with me. About
the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL
commands, assuming the settings are saved in an internal
[EMAIL PROTECTED] (Tom Lane) writes:
Larry Rosenman [EMAIL PROTECTED] writes:
I'd like to see a more concrete definition of what we
want Autovacuum to output and at what levels.
I would argue that what people typically want is
(0) nothing
(1) per-database log
[EMAIL PROTECTED] (Larry Rosenman) writes:
Gentlepeople,
Now that the patch is out for keeping the last
autovacuum/vacuum/analyze/autoanalyze
timestamp in the stats system is pending, what's the consensus view on
what, if any,
logging changes are wanted for autovacuum?
I have the
[EMAIL PROTECTED] (Marc G. Fournier) writes:
To give someone a running chance at migrating it to PostgreSQL, a
'MySQL compatibility module' would allow them to just plug the
existing DB in, and then work at improving sections of the code over
time ...
Hell, if done well, the module should be
[EMAIL PROTECTED] (Mark Woodward) writes:
Jim C. Nasby wrote:
Maybe a compatability layer isn't worth doing, but I certainly
think it's very much worthwhile for the community to do everything
possible to encourage migration from MySQL. We should be able to
lay claim to most advanced and most
[EMAIL PROTECTED] (Andreas Pflug) writes:
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andreas
Pflug
Sent: 31 May 2006 16:41
Cc: Tom Lane; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Possible TODO item: copy to/from pipe
kleptog@svana.org (Martijn van Oosterhout) writes:
On Tue, Jun 13, 2006 at 05:23:56PM -0400, Christopher Browne wrote:
[3]
http://www.intelligententerprise.com/010327/celko_online.jhtml;jsessionid=NDIHEWXGL4TNKQSNDBNSKHSCJUMEKJVN
The sample problem in [3] is one that shows pretty nicely
[EMAIL PROTECTED] (Robert Lor) writes:
For DTrace, probes can be enabled using a D script. When the probes
are not enabled, there is absolutely no performance hit whatsoever.
That seems inconceivable.
In order to have a way of deciding whether or not the probes are
enabled, there has *got* to
[EMAIL PROTECTED] (Csaba Nagy) writes:
[...]
There has to be a more linear way of handling this scenario.
So vacuum the table often.
Good advice, except if the table is huge :-)
... Then the table shouldn't be designed to be huge. That represents
a design error.
Here we have for
[EMAIL PROTECTED] (Marc Munro) writes:
As you see, slony is attempting to enter one tuple
('374520943','22007','0') two times.
Each previous time we have had this problem, rebuilding the indexes on
slony log table (sl_log_1) has fixed the problem. I have not reindexed
the table this time as
[EMAIL PROTECTED] (David Fetter) writes:
On Fri, Jul 07, 2006 at 05:33:14AM -0500, Andrew Dunstan wrote:
Christopher Browne said:
The notion: Plenty of libraries out there like Pg, DBI::Pg, and such
make you specify connections in the form:
host=my.db.host.example.org port=5678
kleptog@svana.org (Martijn van Oosterhout) writes:
On Thu, Jul 13, 2006 at 01:26:30PM -0400, Tom Lane wrote:
The right way to proceed is what was mentioned in another message:
work harder at educating packagers about which non-core projects
are worth including in their packages. I have to
I understand that we have an issue, with Slony-I, concerning the new
standards_conforming_strings option in 8.2.
Slony-I uses the legacy quoting conventions, which, such as it is,
is fine.
If a particular server is set to standards_conforming_strings=on, this
will presumably lead to certain bits
Looks like gBorg has gone down...
The Slony-I project does plan to move to pgFoundry, once 1.2 is released...
http://slony-wiki.dbitech.ca/index.php/Move_to_PgFoundry_Checklist
But we need to get to that point (1.2) first. Alas, gBorg being down
today doesn't help :-(.
--
(format nil [EMAIL
In support of PG 8.2, we need to have the log trigger function do the
following:
- Save value of standards_conforming_string
- Set value of standards_conforming_string to FALSE
- proceed with saving data to sl_log_?
- Recover value of standards_conforming_string
The variable,
[EMAIL PROTECTED] (Peter Eisentraut) writes:
Chris Browne wrote:
In support of PG 8.2, we need to have the log trigger function do the
following:
- Save value of standards_conforming_string
- Set value of standards_conforming_string to FALSE
- proceed with saving data to sl_log_
[EMAIL PROTECTED] (Tom Lane) writes:
Chris Browne [EMAIL PROTECTED] writes:
Unfortunately (perhaps) standards_conforming_strings does not appear
to be exported, so I'm not sure how to do this otherwise.
Perhaps your problem is one of spelling? It's
standard_conforming_strings, and it's
[EMAIL PROTECTED] (Jim C. Nasby) writes:
There are other transactions to consider: user transactions that will
run a long time, but only hit a limited number of relations. These are
as big a problem in an OLTP environment as vacuum is.
Rather than coming up with machinery that will
[EMAIL PROTECTED] (Andrew Dunstan) writes:
Joshua D. Drake wrote:
As a protection against malice, yes. I think Rod was more
interested in some protection against stupidity.
Maybe the real answer is that Slony should connect as a
non-superuser and call security definer functions for the
[EMAIL PROTECTED] (moises) writes:
html xmlns:o=urn:schemas-microsoft-com:office:office
xmlns:w=urn:schemas-microsoft-com:office:word
xmlns=http://www.w3.org/TR/REC-html40;
head
meta http-equiv=Content-Type content=text/html; charset=us-ascii
meta name=Generator content=Microsoft Word 11
Robert Hansen did a talk at OSCON on a compressed annealing framework
called Djinni: http://sixdemonbag.org/Djinni/
It's a framework to use compressed annealing (a derivative of
simulated annealing) for finding approximate solutions to NP-complete
problems such as the TSP with time windows. Note
[EMAIL PROTECTED] (Tom Lane) writes:
Joshua D. Drake [EMAIL PROTECTED] writes:
Well if an initdb was not required, I think that would be a huge feature
;) (I know it may not work release over release)
If someone had started working on pg_upgrade six months ago, we might
have that for 8.2
[EMAIL PROTECTED] (Bruce Momjian) writes:
Christopher Browne wrote:
Make postmater and postgres options distinct so the postmaster -o
option is no longer needed | Alvaro | Confirmed | 09/20/06
Notice the sequence of events. I am not saying the specific statuses are
the way to go but
[EMAIL PROTECTED] (Paul Silveira) writes:
Does anyone have any good examples of implementing snapshot
replication. I know that PostgreSQL does not have snapshot
replication and that Slony-I is the recomended replication senario
but I've configured it and it seems rather advanced for a shop
[EMAIL PROTECTED] (Peter Eisentraut) writes:
Am Mittwoch, 16. August 2006 14:10 schrieb Robert Treat:
I'm not sure I follow this, since currently anyone can email the bugs list
or use the bugs - email form from the website. Are you looking to
increase the barrier for bug reporting?
Only a
[EMAIL PROTECTED] (Jeff Davis) writes:
On Wed, 2006-08-23 at 13:36 +0200, Markus Schiltknecht wrote:
Hannu Krosing wrote:
But if you have very few writes, then there seems no reason to do sync
anyway.
I think there is one: high-availability. A standby-server which can
continue if your
[EMAIL PROTECTED] (Tom Lane) writes:
[EMAIL PROTECTED] (Michael Meskes) writes:
Second try committing the path changes.
Ah, this looks better. I get clean passes on both HPPA in-tree and
Fedora x86_64 VPATH builds, so I think you've finally fixed all the
issues. Congrats!
Ah. So this
[EMAIL PROTECTED] (Michael Meskes) writes:
On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote:
Ah. So this would have caused a bunch of problems in compiling
src/interfaces/ecpg/test/connect/test1.pgc???
Not the compilation errors I would think.
i'm seeing this error when
What's up there? It has been down all week.
We're trying to get the Slony-I 1.2 release out, so we can then
migrate over to pgFoundry. But that doesn't working terribly well
when gBorg's down...
--
let name=cbbrowne and tld=acm.org in String.concat @ [name;tld];;
[EMAIL PROTECTED] (Tom Lane) writes:
Chris Browne [EMAIL PROTECTED] writes:
If I touch preproc.y and pgc.l, the .c files get regenerated, and all
is well.
If I don't, they get left alone, and I see compilation errors.
It seems to me you need to rebuild the C files and commit them
[EMAIL PROTECTED] (elein) writes:
Also people trying to download slony have to do some
hunting to find things. The source only tar is not
available on pgfoundry.
The source tarball for version 1.1.5 is now in place:
http://pgfoundry.org/frs/download.php/1063/slony1-1.1.5.tar.bz2
We may as
[EMAIL PROTECTED] (Magnus Hagander) writes:
Also people trying to download slony have to do some hunting
to find things. The source only tar is not available on pgfoundry.
All gborg *downloads* are available on:
http://www.postgresql.org/ftp/projects/gborg/
Seems Slony hasn't released
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:
http://www.nilfs.org/en/
NILFS is a
[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 AIX);
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
[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 Systems Review (this is the first time
I've
[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 pulling the
[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.
AIX 4.3 is the first
[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 that we
[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 in 8.3.
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 tables.
I'd suggest looking at the section
[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
I've got a case where I need to reverse strings, and find that, oddly
enough, there isn't a C-based reverse() function.
A search turns up pl/pgsql and SQL implementations:
create or replace function reverse_string(text) returns text as $$
DECLARE
reversed_string text;
incoming alias for $1;
[EMAIL PROTECTED] (hubert depesz lubaczewski) writes:
On Mon, Sep 08, 2008 at 11:20:18AM -0400, Chris Browne wrote:
I've got a case where I need to reverse strings, and find that, oddly
enough, there isn't a C-based reverse() function.
A search turns up pl/pgsql and SQL implementations:
just
[EMAIL PROTECTED] (Heikki Linnakangas) writes:
Simon Riggs wrote:
Taking snapshots from primary has a few disadvantages
...
* snapshots on primary prevent row removal (but this was also an
advantage of this technique!)
That makes it an awful solution for high availability. A
[EMAIL PROTECTED] (Gevik Babakhani) writes:
It might look like an impossible goal to achieve.. But if there is
any serious plan/idea/ammo for this, I believe it would be very
beneficial to the continuity of PG.
Actually, I imagine that such a rewrite would run a very considerable
risk of
[EMAIL PROTECTED] (Heikki Linnakangas) writes:
Log Message:
---
Make LC_COLLATE and LC_CTYPE database-level settings. Collation and
ctype are now more like encoding, stored in new datcollate and datctype
columns in pg_database.
This is a stripped-down version of Radek Strnad's
[EMAIL PROTECTED] (Gevik Babakhani) writes:
Advantage of C++ is that it reduce lot of OO code written in
C in PostgreSQL, but it is so big effort to do that without
small gain. It will increase number of bugs. Do not forget
also that C++ compiler is not so common (so good) on
different
1 - 100 of 252 matches
Mail list logo
