u want to change, and then
omit it from the restore).
Custom format rocks for partial set restores from a whole dump. See the
TOC option :)
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
Andrew Dunstan wrote:
Joshua D. Drake wrote:
Agreed but that is a problem I understand with a solution I don't. I
am all eyes on a way to fix that. One thought I had and please, be
gentle in response was some sort of async transaction capability. I
know that libpq has the ability to
Simon Riggs wrote:
On Sat, 2008-07-26 at 11:03 -0700, Joshua D. Drake wrote:
2. We have no concurrency which means, anyone with any database over 50G
has unacceptable restore times.
Agreed.
Sounds good.
Doesn't help with the main element of dump time: one table at a time to
one o
ease
of 7.2, pg_dump -A please.
Anyway, I leave other peeps to flame me into oblivion.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http:
isable it.
I believe so. This was when not everyone was convinced. Im fairly
certain Josh original patch is in the commit fest. So feel free to
drop this one.
My patch has been committed.
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes t
s rather than figure out
> the OUT parameter syntax afresh.
Regardless of whether anyone thinks they are byzantine (or not) if
RETURNS TABLE() is in the standard. We should try and implement it if we
can.
Sincerely,
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postg
Hans-Juergen Schoenig wrote:
Gregory Stark wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
i don't think statement_timeout is a good idea at all.
it is not deterministic. depending on the load on the server some
queries will execute while others fail.
a separa
separate guc variable which limits the maximum number of
> levels of recursive iterations. That might be a useful feature for DBAs that
> want to limit their users from issuing an infinite query.
>
statement_timeout :)
Joshua D. Drake
--
Sent via pgsql-patches mailing lis
stand an updating to reflect how development
currently commences. I will work up a patch next week.
Joshua D. Drake
-dg
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
the effort.
Sincerely,
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
ve burned all the time during commit fest only.
Now Alvaro, Tom and I are all having the same discussion all over again
but this time with Bruce. It makes no sense.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Con
to the patch
in all this wrangling is realign the \? General options and frankly even
that is suspect in my opinion. Can we either throw it away and say,
"Nice try JD" or just commit the thing.
Joshua D. Drake
regards, tom lane
--
Sent via pgsql-patche
Bruce Momjian wrote:
Joshua D. Drake wrote:
Bruce Momjian wrote:
I moved '\g' up into the "General" section rather than make it a
single-entry section.
"send query buffer to server means nothing to a newbie". You execute
queries, you don't send buffers (fr
ns nothing to a newbie". You execute
queries, you don't send buffers (from a user perspective).
Sincerely,
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
esql.org/pgsql-hackers/2008-04/msg01476.php
And most specifically:
http://archives.postgresql.org/pgsql-hackers/2008-04/msg01376.php
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
t frequently-used help commands?
Aren't they at the top of \?.
The purpose of help is to provide what help options there are available
to those who need them.
Joshua D. Drake
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
rkloads with
> PostgreSQL. Let's hope those disks get delivered to Portland soon. :)
I have those disks.
Joshua D. Drake
>
> Regards,
> Mark
>
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconfere
n thinking
about it, this might actually be a foot gun. You have a new pg guy,
download source and think to himself..., "Hey I have a 4k block size as
formatted on my hard disk". Then all of a sudden they have an
incompatible PostgreSQL with everything else.
Sincerely,
Joshua D.
On Wed, 23 Apr 2008 14:41:20 -0700
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
Hello,
Per final discussion here:
http://archives.postgresql.org/pgsql-hackers/2008-04/msg01607.php
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
Post
help for help only
* if server doesn't match shows server version too
* if there is a major version mismatch it throws a warning
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference:
was a joke domain name, like Pen Island.com.
>
Its not and a lot of postgresql users interact there.
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association:
is bogus. We are an Open Source
database, let others worry about obfuscation. It isn't like it can't be
done within the facilities that already exist.
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postg
On Sat, 05 Apr 2008 16:37:15 +0100
Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
May I just say that every person that is currently talking on this
thread is offtopic? Move it to -hackers please.
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
Post
at
it didn't offer what I thought it did.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to
ity that needs to be properly designed.
Please see my later email on the thread.
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgres
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 03 Apr 2008 21:26:46 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > I would agree with this. We would need a history of checkpoints that
> > didn't reset
orking is valuable but... being able to
say, "SELECT * FROM give_me_my_db_info;" is much more useful in this
context.
In short, I should never have to go to log for this class of
information. It should be available in the database.
Sincerely,
Joshua D. Drake
- --
The Postgr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 03 Apr 2008 20:29:18 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
> >> Why is that useful?
>
&g
ng how long checkpoints are taking. If they are taking too
long you may need to adjust your bgwriter settings, and it is a
serious drag to parse postgresql logs for this info.
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 03 Apr 2008 00:57:11 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Tom Lane <[EMAIL PROTECTED]> wrote:
> >> The fundamental problem I've got wi
ch prefer it be cleaned up
into its own space.
>
> The idea would be a lot easier to swallow if the code were refactored
> to avoid the duplication with plpgsql.
+1.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Commun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Mar 2008 18:30:46 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> Which part of "this is the wrong list" wasn't clear to you guys?
I actually didn't even notice. Sorry Tom.
Joshua D. Drake
- --
The Postgr
ument that has compelled me to actually
want to have us enter the Gnome world of binary naming.
However, if we *must* go down this route let us please use pgcreatedb
*not* pg_createdb.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt
g rpms. Thanks for this
- -hackers.
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liai
Tom very seriously.
Andrew is absolutely correct here. If you do not agree with Tom, you
best prove why. Otherwise your patch will likely be ignored on
submission.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564
Pavel Stehule wrote:
Wrong address :)
O.k. now that makes more sense :)
Joshua D. Drake
Pavel
On 12/12/2007, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
While looking at the package function precedence problem, I bumped into
another unrelated bug:
---(
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
As of PG 8.3, libpq allows a conninfo string to be passed in via the
dbName parameter of PQsetdbLogin.
I didn't even know we could do that. I always use the shell variable
option instead. Doe
nestly using this that
isn't smart enough to just figure out it isn't supported.
Joshua D. Drake
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
says, "Yo... I need to restart
postgresql, please stop all productive tasks on your end because I am
more important."
+1 on enabling client side behavior.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Nov 2007 17:29:51 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
> > Heh, o.k. that was an ambiguous sentence. In a partitioned
> > environment yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Nov 2007 17:08:29 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
>
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
> > Tom Lane wrote:
> >
> >> A trigger will probably beat a rule
Bruce Momjian wrote:
Joshua D. Drake wrote:
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Rules are extremely slow in comparisons and not anywhere near as
flexible. As I said up post yesterday... they work well in the basic
partitioning configuration but an
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Rules are extremely slow in comparisons and not anywhere near as
flexible. As I said up post yesterday... they work well in the basic
partitioning configuration but anything else they are extremely deficient.
flawlessly for us,... so personally I don't even know the reasons.
Rules are extremely slow in comparisons and not anywhere near as
flexible. As I said up post yesterday... they work well in the basic
partitioning configuration but anything else they are extremely deficient.
Joshua D. Drake
seeing that construct in real
> databases.
And they could refer back to the older version of the documentation for
it. In fact, we should mention that in the patch:
If you have an partitioning setup that uses rules please
refer to the 8.2 documentation on partitioning
Sincer
g configuration.
However rules are so deficient on anything except the absolute most
basic example of partitioning that I think we are doing our new
partitioning users a disservice by stating anything about rules except
in passing.
Sincerely,
Joshua D. Drake
>
> Cheers,
> David.
- --
ch
> reflects this.
>
> Thanks to Robert Treat for help putting this together :)
>
> Cheers,
> David.
+1
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions sinc
g".
>
> Any other bids?
XML tag is fine, imo.
Sincerely,
Joshua D. Drake
>
> cheers
>
> andrew
>
> ---(end of
> broadcast)--- TIP 5: don't forget to increase
> your free space map settings
>
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 4 Nov 2007 14:18:23 -0500 (EST)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Stefan Kaltenbrunner wrote:
> > Joshua D. Drake wrote:
> > > On Sun, 04 Nov 2007 13:24:54 -0500
> > > Tom Lane <[EMAIL PROTEC
e the configure says exactly that.
If not, it isn't that big of a deal. I was just making a suggestion to
try and help stop confusion in the future.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emerge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 04 Nov 2007 13:24:54 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Shouldn't --with-libxml be noted as deprecated?
>
> Huh?
Because in 8.3 it is in co
t;
> I have modified the configure message to be:
>
> --with-libxslt build /contrib/xml2 with XSLT support
>
> Patch attached.
Shouldn't --with-libxml be noted as deprecated?
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sale
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua D. Drake wrote:
> Tom Lane wrote:
>> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>>> Here is a patch that documents the syslog log levels and their
>>> correlation to the PostgreSQL log levels per:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> Here is a patch that documents the syslog log levels and their
>> correlation to the PostgreSQL log levels per:
>
> This seems like quite the wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Here is a patch that documents the syslog log levels and their
correlation to the PostgreSQL log levels per:
http://archives.postgresql.org/pgsql-general/2007-09/msg00982.php
Joshua D. Drake
- --
=== The PostgreSQL Company: Command
think about it,
it really is clunky and doesn't serve any real purpose.
Joshua D. Drake
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresq
spaced applications out there are in the G/K world
of nome and de.
Joshua D. Drake
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
on changes to make?
Well here is a question (just because I haven't seen it) is there a list
of functions and their volatility in the docs?
Joshua D. Drake
regards, tom lane
---(end of broadcast)---
TIP 4: Have
rd behaviour on standard syntax?
So much for hypocrisy.
Antagonism will not help your cause.
Joshua D. Drake
--- pgsql.orig/src/backend/catalog/heap.c 2007-05-15 09:34:25.0
+0200
+++ pgsql/src/backend/catalog
s more appropriate.
Is it more efficient in other ways besides negligible tps? Possibly more
efficient memory usage? Better restore times for a crashed system?
Sincerely,
Joshua D. Drake
>
> Regards;
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support:
imited by the DBA; certainly much simpler than
the vacuum cost limiting feature.
+1
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
Alvaro Herrera wrote:
Hi,
uhmmm patch?
Here is the autovacuum patch I am currently working with. This is
basically the same as the previous patch; I have tweaked the database
list management so that after a change in databases (say a new database
is created or a database is dropped), the
Peter Eisentraut wrote:
> Mike Rylander wrote:
>> A related question, however: Will the XML features being included in
>> 8.3 support namespace prefix registration?
>
> That is certainly the plan.
Let me bounce my ostrich (sp?) head up here and say, thanks for your
work on
/www.nabble.com/POSIX-shared-memory-support-t3298386.html
Which happens to be you ;)
Sincerely,
Joshua D. Drake
>
> Thanks again,
> Chris Marcellino
>
>
>
>
>
>
>
> ---
> appropriate person.
>
> Rgds,
> Arul Shaji
I know that I can speak for the community when I say, Thanks to you and
Fujitsu for taking our concerns into consideration.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.
ailing list signup pages and the welcome
pages to the lists.
Joshua D. Drake
>
>
> ---
>
> Tom Lane wrote:
>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>>> Neil Conway wrote:
>>>>
sclosure, it isn't our fault the
recipients didn't listen."
Of course the joke here is, that the email went out on a public list and
is now mirrored all over the world and harvested by every spammer on the
planet ;)
However, it may be a good idea to have our (SPI) attorney at least give
u
that checks for signatures with specific
legal words and strips said signature automatically, responding to the
sender that we did so.
Joshua D. Drake
>
> regards, tom lane
>
> ---(end of broadcast)-
Neil Conway wrote:
> On Tue, 2007-02-27 at 14:52 -0800, Joshua D. Drake wrote:
>> Gonna have to concur with that. Not that the sig is legally binding
>> anyway, we do need to have a disclaimer in the email stating that you
>> are assigning to PGDG
>
> I think it
he email stating that you
are assigning to PGDG>
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandpro
.
COPY would be a good option, but INSERT is probably what I would use as
the default. The most use I see for this is something where I am tailing
out the log and inserting live into a log db...
Sincerely,
Joshua D. Drake
>
> Rgds,
> Arul Shaji
>
>
>
>>
.
To me, it is a clear line. Once we accept for one, we may accept for
another.
Sincerely,
Joshua D. Drake
>
> -Neil
>
>
>
> ---(end of broadcast)---
> TIP 1: if posting/reading through Usenet, please send an appropriate
Joshua D. Drake wrote:
> Alvaro Herrera wrote:
>> Joshua D. Drake wrote:
>>> Peter Eisentraut wrote:
>>>> Magnus Hagander wrote:
>>>>> That also requires a "reasonable shell", which all platforms don't
>>>>> have...
Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>> Peter Eisentraut wrote:
>>> Magnus Hagander wrote:
>>>> That also requires a "reasonable shell", which all platforms don't
>>>> have...
>>> I think doing any sort of reasonabl
plementing loops and
> conditionals in psql.
... Now that you mention it :)
psql is a shell. It is the postgresql shell. I don't see any problem
with continuing to extend the postgresql shell to a more functional
platform that is independent.
Sincerely,
Joshua D. Drake
--
gt;
> MultiCid, like the MultiXacts? Maybe not, they're quite different beasts...
>
> Alias cid? Mapped cid? Compressed cid? Hero cid? :)
>
> I'm happy with phantom cid myself. It sounds cool, and they are a bit
> phantom-like because the true meaning of a phant
Bruce Momjian wrote:
> What is the status of this patch?
Alvaro is currently out of town. He should be able to provide more info
next week.
Sincerely,
Joshua D. Drake
>
> ---
>
> Alvaro Herrera wrote:
&g
database?
ALTER DATABASE foo SET uuid_salt =
:)
That would be pretty cool, but I am sure most will shoot that down in
flames :)
Sincerely,
Joshua D. Drake
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.224
ng things in the marketplace
and professional communities.
It is time we stop fighting features for the sake of fighting features.
Sincerely,
Joshua D. Drake
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing
Bruce Momjian wrote:
> Takayuki Tsunakawa wrote:
>> From: "Bruce Momjian" <[EMAIL PROTECTED]>
>> Yes, you are 100% correct that I had exceptions and errors confused.
>> I
>>> have backed out the patch that used FormatMessage(), and instead of
>>> using a URL, the message is now:
>>>
>>> child proc
Joshua D. Drake wrote:
>> Per previous discussion, the main problem with a uuid type is the
>> new-uuid generator function, which tends to involve a bunch of
>> not-so-portable assumptions and code. If we accept a uuid type in
>> either core or contrib, all of a sudden
to use.
A generator would be great too of course, but if they really need one
they could use one of the pl languages for it.
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
> ---(end of broadcast)---
> TIP 1:
On Thu, 2007-01-11 at 21:05 -0500, Jaime Casanova wrote:
> On 1/11/07, Albert Cervera Areny <[EMAIL PROTECTED]> wrote:
> > Please, go on with that, I hadn't seen that problem. Indeed, I read Andrew
> > answer to your question and I think it's a nice solution.
> >
>
> yes... i'm always trying to ki
would argue that most do not know. It
isn't intuitive to the process. You *expect* that an index will be made.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most com
On Sat, 2007-01-06 at 22:09 -0500, Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> >> cost is having to fsync the whole table afterwards. So it really only
> >> makes sense for commands that one can expect are writing pretty much
> >
> cost is having to fsync the whole table afterwards. So it really only
> makes sense for commands that one can expect are writing pretty much
> all of the table. I could easily see it being a net loss for individual
> INSERTs.
What about multi value inserts? Just curious.
Joshua D
ts that it
> will be in WAL. The default would be use_wal_in_copy = true.
That I don't think makes sense. A copy is an all or nothing option, if a
copy fails in the middle the whole thing is rolled back.
Sincerely,
Joshua D. Drake
>
>
--
=== The PostgreSQL Com
AL logged.
No I don't see any problems, I am just trying to understand the
boundaries. E.g., is there some weird limitation where if I have any
values in the table before the copy (like the example above) that copy
will go through WAL.
Or in other words, does this patch mean that all COPY executi
; > for COPY in these circumstances:
> >
> > BEGIN;
> > CREATE TABLE foo..
> > COPY foo...
> > COMMIT;
What if I do this?
BEGIN;
CREATE TABLE foo...
INSERT INTO foo VALUES ('1');
COPY foo...
COMMIT;
?
E.g., what are the boundari
.
Real world dictates differently. Let's not forget that not every company
can spend 100k on two identical machines, yet many companies can spend
50k + 5k for a backup machine based on Sata or secondary services.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Comman
> I get 'inf'. I am on BSD and just tested it on Fedora Core 2 and got
> 'inf' too.
Ubuntu Edgy 64bit on Athlon 64X2 returns inf.
Joshua D. Drake
>
> > A slightly less radical proposal is to reject only the case where
> > isinf(result) and neither
> The current terminology of live and dead is already used in many places in
> the
> documentation and in userspace; mostly around the need for maintainance of
> dead tuples within tables, reindex cleaning up dead pages, and even in the
> vacuum commands output (n dead tuples cannot be removed
On Tue, 2006-12-26 at 13:59 -0800, Glen Parker wrote:
> I'd love to see this back patched into 8.2.1 if possible.
Probably not. We typically do not introduce new features into back
releases.
Sincerely,
Joshua D. Drake
>
> Should I resubmit with new names?
>
> -Glen
>
On Mon, 2006-11-27 at 17:58 -0500, Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > On Mon, 2006-11-27 at 17:48 -0500, Tom Lane wrote:
> >> I do not see the point of this. Shall we put equivalent disclaimers
> >> into every s
de
available to the operating system (well dynamic, but statically
configured).
Joshua D. Drake
> There is no
> such paragraph under LOCK TABLE, for example.
>
> regards, tom lane
>
> ---(end of broadcast)
Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> Here is adminpack...
>
> Applied with minor corrections (the .sql file is DATA not DATA_built,
> as you'd have found out if you'd tried "make clean").
Ooops :)
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
? libpgrowlocks.so.0.0
? pgrowlocks.diff
? pgrow
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
? adminpack.diff
? adminpack.sql
? libadminpack.so.0.0
?
Hello,
Here is adminpack...
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
? adminpack.diff
? adminpac
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED] on behalf of Jonah H. Harris
Sent: Sun 8/27/2006 3:24 AM
To: Joshua D. Drake
Cc: Andrew Dunstan; Bruce Momjian; Tzahi Fadida; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Adding fulldisjunctions to the contrib
It&#
1 - 100 of 153 matches
Mail list logo
