python3u
template1".
Am I doing something incorrect, or...?
(As an aside, functions created with LANGUAGE plpython3u appear to work.)
--
Chris Spotts
rfu...@gmail.com
s file
"$libdir/plpython3": No such file or directory
Thoughts? Ideas? Am I doing something wrong? If I can provide more detail
about something specific, let me know.
--
Chris Spotts
rfu...@gmail.com
ly, "What's New In Python
3.0<http://docs.python.org/dev/3.0/whatsnew/3.0.html> "
for the beta 3 docs on
http://www.postgresql.org/docs/9.0/static/plpython-python23.html is dead.
On Tue, Jul 13, 2010 at 4:02 PM, Peter Eisentraut wrote:
> On tis, 2010-07-13 at 15:38 -0500,
>
>
> You'd have to build the two plpython.so's in separate compile operations.
>
>regards, tom lane
>
I hadn't thought of that. Tried it and it does work. Thanks.
--
Chris Spotts
rfu...@gmail.com
[EMAIL PROTECTED] ("Marko Kreen") writes:
> Also the design should be based on assumption that the target side
> is exactly in sync. Eg. DROP CASCADE should be replicated as DROP CASCADE.
> We should not make scheme more complex to survive cases where target
> is not in sync. That way madness lie
[EMAIL PROTECTED] (Markus Wanner) writes:
> as you might know, Postgres-R relies on primary keys to address tuples
> of a table. It cannot replicate tables without a primary key.
Slony-I does the same, with the "variation" that it permits the option
of using a "candidate primary key," namely an in
[EMAIL PROTECTED] (Markus Wanner) writes:
> Hello Chris,
>
> chris wrote:
>> Slony-I does the same, with the "variation" that it permits the option
>> of using a "candidate primary key," namely an index that is unique+NOT
>> NULL.
>>
>> I
[EMAIL PROTECTED] (Markus Wanner) writes:
> chris wrote:
>> I agree with you that tables are *supposed* to have primary keys;
>> that's proper design, and if tables are missing them, then something
>> is definitely broken.
>
> Ah, I see, so you are not concerned
Dimitri Fontaine <[EMAIL PROTECTED]> writes:
> Note that while slony doesn't require a dump/restore to get activated, it
> seems to me (as a non user of it) that it still plays with catalog,
> preventing "normal" usage of pg_dump...
FYI, that will no longer be the case in version 2.0 of Slony-I;
[EMAIL PROTECTED] (Simon Riggs) writes:
> Every time we introduce a feature that changes output, we just put an if
> test in saying sql_compatibility = X, (the release we added feature).
>
> Straightforward, futureproof. Cool.
This is somewhat like the way that some shells try to emulate others;
f
[EMAIL PROTECTED] ("Ken Camann") writes:
> On Thu, Jul 3, 2008 at 12:39 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> "Ken Camann" <[EMAIL PROTECTED]> writes:
>>> EMT64/AMD64 is new compared to the older architectures, I
>>> would guess the older ones predate the time when it became a somewhat
>>> de
Hi,
I'm playing around with the CVS version and noticed a change from 7.2 in
regards to serial datatypes - they no longer automatically have an
index. Is this a deliberate thing? I did a search in the archives but
didn't come across mention of the change. A pointer to discussion on
this would
an anyone shed some light on this just by looking at it? Two of us have wasted
basically an entire day getting to this point and would appreciate any assistance. We
may end up having to settle with 64 characters and install the latest RC :-) However
ideall
y spinlock code
for the R5900?
If that's not worth the trouble, would it be a good idea to have
configure disable spinlocks automagically on unsupported platforms?
Or is it to hard to autodetect this?
Bye, Chris.
PS: I've compiled using gcc 2.95.2 and with CFLAGS -O0 -g.
*** ./exp
> http://www.pgsql.ru/
> We are welcome your feedback and comments.
Very nice work!
I've just found some docs I was looking for a long time :)
Bye, Chris.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
=cern+event+database+postgresql
or even
http://www.google.com/search?q=cern+event+database
You might find some inspiration there!
Bye, Chris.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.or
e I have table a and b (b inherits a).
>
> Then I do select * from a*;
>
> Now, I'd like to know which table this particular row came from (a or b).
> Is this possible? Or do I have to have a column where I'd store what kind
> of object this is?
>
> -ale
osov wrote:
>
> Can I do following?
>
> create table foo (
> x int4 references bar*
> )
>
> Or, since 7.1 will have bar* as default for bar, will using 'references
> bar' do what I want?
>
> -alex
--
Chris Bitmead
mailto:[EMAIL PROTECTED]
http://www.techphoto.org - Photography News, Stuff that Matters
There is some stuff which last time I looked is in contrib that allows
queries to test if something is in an array. Something vaguely like
SELECT * from part, box where IN(part.num, box.array).
Having this integrated in the foreign key stuff would certainly be
important for object databases, whic
KuroiNeko wrote:
> 1 create table alpha( id int4, payload text );
> Not a big deal, right?
Yes a big deal. You just lost all your oids.
Hiroshi Inoue wrote:
> When I used Oracle,I saw neither option of DROP
> COLUMN feature. It seems to tell us that the
> implementation isn't
> that easy. It may not be a bad choise to give up DROP
> COLUMN feature forever.
Because it's not easy we shouldn't do it? I don't think so. The perfect
Hiroshi Inoue wrote:
> Certainly it would need 2x.
> However is ADD COLUMN DEFAULT really needed ?
> I would do as follows.
>
> ADD COLUMN (without default)
> UPDATE .. SET new_column = new default
> ALTER TABLE ALTER COLUMN SET DEFAULT
Well in current postgres that would use 2x. Wi
Hiroshi Inoue wrote:
> We could easily break the consistency of DB due to
> careless implementations.
I'm sure no-one around here would do careless implementations. :-)
Alfred Perlstein wrote:
> Thank you, it's not a big problem that this doesn't happen, but it'd
> be nice to see it as an option when creating a table via inheritance.
>
> What about RULEs? I wouldn't really have a use for that but others
> might.
Actually it's a reasonably big deal. Apart from
E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
>
> "Delight thyself also in the LORD; and he shall give
> thee the desires of thine heart." Psalms 37:4
--
Chris Bitmead
mailto:[EMAIL PROTECTED]
Hiroshi Inoue wrote:
> > At the end of the day though, the reason is only performance. The
> > semantics should be the same no matter whether implemented as multiple
> > indexes or not. Performance is much better with one index though.(*)
> >
>
> Is it true ?
> How to guarantee the uniqueness us
> The point is: this is classic, but noone does it
> like this if your really have a larger hierarchy of
> classes. You'll not get any good performance, when
> solving an association in your oo
> program, because the framework has to query against
> each table: 6 tables - 6 queries !!! :-(((
Marten Feldtmann wrote:
> > You'll still have to do 6 queries in postgres because it does not return
> > fields in sub-classes.
>
> Practically this is not such a big problem as one might think.
> WHEN you have a persistance framework you tell your framework,
> that every attribut is located
fno-common flag and see if
that fixes things.
Thanks Tom for spending part of your weekend on this.
Chris.
> On Mar 12, 2016, at 17:58, Tom Lane wrote:
>
> I wrote:
>> That's confusing because it implies that -fno-common is the default,
>> which it evidently is not. But
ore descriptive name but
currently did not remove the old function yet.
Feedback is very welcome. pg_rewind is a very nice piece of software. I
am hoping that these sorts of changes will help ensure that it is easier to
use and provides more predictable results.
--
Best Regards,
Chris T
settings.
3. In a subsequent stage you might be able to SELECT INTO
setting_name FROM ; allowing access to setting writes based on queries.
> regards
>
> Pavel
>
>
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
ter the output.
>
> Regards
>
> Pavel
>
>
>
>
>>
>>
>>> regards
>>>
>>> Pavel
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Chris Travers
>> Database Administrator
>>
&
First, thanks for your thoughts on this, and I am interested in probing
them more.
On Mon, Oct 30, 2017 at 9:04 AM, Michael Paquier
wrote:
> On Sat, Oct 28, 2017 at 4:22 AM, Chris Travers
> wrote:
> > The Solution:
> > The solution is a whitelist of directories specified
On Mon, Oct 30, 2017 at 10:57 AM, Michael Paquier wrote:
> On Mon, Oct 30, 2017 at 9:43 AM, Chris Travers
> wrote:
> > Are there any cases right now where you have features added by
> extensions that write to directories which are required for a rewind?
>
> In some of th
On Mon, Oct 30, 2017 at 11:36 AM, Michael Paquier wrote:
> On Mon, Oct 30, 2017 at 10:15 AM, Chris Travers
> wrote:
> > This also brings up a fairly major concern more generally about control
> by
> > the way. A lot of cases where pg_rewind is called, the user doesn't
d2fa1
tag: mine/pg_rewind_restrict_dirs
parent: 60446:e638ba9c3c11
user: Chris Travers
date:Mon Oct 30 12:25:18 2017 +0100
files: doc/src/sgml/ref/pg_rewind.sgml src/bin/pg_rewind/copy_fetch.c
src/bin/pg_rewind/fetch.c src/bin/pg_rewind/fetch.h
src/bin
ns of PostgreSQL to bump this
setting up to ever higher values, I am wondering if anyone has done this
yet and if so if you would be willing to share results.
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a,
On Tue, Oct 31, 2017 at 1:38 PM, Robert Haas wrote:
> On Mon, Oct 30, 2017 at 6:44 PM, Chris Travers
> wrote:
> > The attached patch is cleaned up and filed for the commit fest this next
> > month:
>
> It's generally better to post the patch on the same message as t
upport different use cases
well and then build common infrastructure to support the different cases.
I am not against building common infrastructure for pg_rewind and
pg_basebackup. I am very much against having the core guarantees being the
exact same.
Best Wishes,
Chris Travers
On Sat, Oct 28, 20
y
causing the problem. My guess is that either you didn't declare the type
properly or there is some other error in your function, but the information
provided is not sufficient to answer it.
Best or luck asking on -general.
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
:
SET VARIABLE foo='bar';
Perhaps one can have a short form of:
SET VAR foo = 'bar';
vs
SET foo = 'bar'; -- GUC
>
> regards, tom lane
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make c
y.sql and
foo--[version]--unset-parallel-safety.sql
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
hings from
happening in the future if, for example, a replica dies in the middle of a
wal fsync.
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
Sorry, meant to reply all.
On Thu, Aug 10, 2017 at 2:19 PM, Vladimir Borodin wrote:
> Hi, Chris.
>
> 10 авг. 2017 г., в 15:09, Chris Travers
> написал(а):
>
> Hi;
>
> I ran into a funny situation today regarding PostgreSQL replication and
> wal corruption and wan
pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
pageaddr 1E375/61118000 in log segment 0001E39C00E1, offset
1146880
> --
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
of
this size.
>
> Likelihood of two different persons seeing similar error message just a
> year apart is low. From our practice hardware corruption usually looks like
> a random single bit flip (most common - bad cpu or memory), bunch of zeroes
> (bad storage), or bunch of complet
On Fri, Aug 11, 2017 at 1:33 PM, Greg Stark wrote:
> On 10 August 2017 at 15:26, Chris Travers wrote:
> >
> >
> > The bitwise comparison is interesting. Remember the error was:
> >
> > pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
&
On Fri, Aug 11, 2017 at 1:33 PM, Greg Stark wrote:
> On 10 August 2017 at 15:26, Chris Travers wrote:
> >
> >
> > The bitwise comparison is interesting. Remember the error was:
> >
> > pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
&
various
operations including creating materialised views.
So my question is if there is a way we can safely clean these up on server
restart? If not does it make sense to try to create a utility that can
connect to PostgreSQL, seek out valid files, and delete the rest?
--
Best Regards,
Chris Travers
On Aug 14, 2017 14:12, "Chris Travers" wrote:
Hi all;
I am trying to track down a problem we are seeing that looks very similar
to bug #12050, and would certainly consider trying to contribute a fix if
we agree on one. (I am not sure we can, so absent that, the next question
is
On Mon, Aug 14, 2017 at 6:33 PM, Andres Freund wrote:
> Hi,
>
> On 2017-08-14 14:12:22 +0200, Chris Travers wrote:
> > Problem:
> > The system this came up on is PostgreSQL 9.6.3 and has had repeated
> trouble
> > with disk space. Querying pg_database_size, as well
ions
but that I might be able to do.
>
> regards, tom lane
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
we
ought to be able to know that a relfilenode shouldn't be used anymore,
right?
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
On Tue, Aug 15, 2017 at 3:32 PM, Tom Lane wrote:
> Chris Travers writes:
> > I wonder about a different solution. Would it be possible to special
> case
> > vacuum to check for and remove (or just move to where they can be
> removed)
> > files when vacuuming pg_
make
sure everything is ok?
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
l programs to do after-the-fact
review and cleanup.
>
> Greetings,
>
> Andres Freund
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
hear it.
>
> [1] https://www.postgresql.org/message-id/c8fe4f6b-ff46-aae0-89e
> 3-e936a35f0cfd%40postgrespro.ru
>
> Thanks!
>
> --
> Ildar Musin
> i.mu...@postgrespro.ru
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make chang
e data models pluggable,
> especially related to plugging the parser, planner, executor, etc?
> One possible concern is that various PostgreSQL components might be
> too dependent on the data model being relational, and it would be
> difficult to separate tight coupling.
>
I guess I am m
On Sun, Aug 20, 2017 at 4:10 AM, MauMau wrote:
> From: Chris Travers
> > Why cannot you do all this in a language handler and treat as a user
> defined function?
> > ...
> > If you have a language handler for cypher, why do you need in_region
> or cast_region? Why n
On Aug 21, 2017 07:47, "Simon Riggs" wrote:
On 18 August 2017 at 15:40, Alvaro Herrera wrote:
> Ildar Musin wrote:
>
>> While we've been developing pg_pathman extension one of the most frequent
>> questions we got from our users was about global index support. We cannot
>> provide it within an e
ailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
y of moving forward.
But I still think the question of what to test ought to be geared around
"what are we willing to try to guarantee as behaviour for some years, not
just to ourselves but to third parties."
>
> Greetings,
> Torsten
>
>
> --
> Sent via pgsql-hacker
On Fri, Aug 25, 2017 at 12:15 PM, Petr Jelinek wrote:
> On 25/08/17 10:28, Chris Travers wrote:
> >
> >
> > On Thu, Aug 24, 2017 at 9:44 PM, Andres Freund > <mailto:and...@anarazel.de>> wrote:
> >
> > Hi,
> >
> > On 2017-08-18
file tree traversal.
Any feedback before I create.a proof of concept?
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
of any cases where anyone would actually
want to do this but that doesn't mean they aren't out there. If people
really want to, then they need to copy the configuration files they want
separately.
Next Steps:
If people like this idea I will add test cases and edit documentation as
app
sequently, I think it would be good to fix in the tool. The
fundamental question is if there is any reason someone would actually want
to copy config files over.
--
> Michael
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
On Mon, Sep 4, 2017 at 3:38 PM, Alvaro Herrera
wrote:
> Chris Travers wrote:
> > On Mon, Sep 4, 2017 at 12:23 PM, Michael Paquier <
> michael.paqu...@gmail.com>
> > wrote:
> >
> > > On Mon, Sep 4, 2017 at 7:21 PM, Michael Paquier
> > > wr
On Tue, Sep 5, 2017 at 12:54 PM, Vladimir Borodin wrote:
>
> 5 сент. 2017 г., в 12:31, Chris Travers
> написал(а):
>
> I think the simplest solution for now is to skip any files ending in
> .conf, .log, and serverlog.
>
>
> Why don’t you want to solve the problem once
On Tue, Sep 5, 2017 at 1:04 PM, Michael Paquier
wrote:
> On Tue, Sep 5, 2017 at 7:54 PM, Vladimir Borodin wrote:
> > 5 сент. 2017 г., в 12:31, Chris Travers
> > написал(а):
> >
> > I think the simplest solution for now is to skip any files ending in
> .conf,
>
under heavy load.
>
How would this work when it comes to rewinding against a file directory?
>
> --
> May the force be with you…
> https://simply.name
>
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
undo subsystem would fix this.
Is this a reason to rethink the idea that maybe a pg_fsck utility might be
useful that could be run immediately after a rewind?
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
tion of a small table. I
don't see an easy or safe way to address that from inside pg_rewind without
a lot of complication. It might be better to have a dedicated tool for
that.
>
> Now, in order for any of this to happen, there will need to be a
> champion to define what the mis
.
Problems that we will not try to solve:
* Rewinding past table creation orphans table file. This is a complex
topic on its own and probably needs a separate utility.
Thoughts?
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
On Wed, Sep 13, 2017 at 6:28 AM, Michael Paquier
wrote:
> On Tue, Sep 12, 2017 at 11:52 PM, Chris Travers
> wrote:
> > Additionally the wal, xact, timestamp and logical directories must be
> > processed in some way.
>
> To what does the term "logical directories&
!: dfetter
> Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
>
> Remember to vote!
> Consider donating to Postgres: http://www.postgresql.org/about/donate
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
comment away any time you please.
Well, I don't know if my feedback above is helpful, but there it is ;-)
>
>
> Regards,
> Marko Tiikkaja
>
> [1]: http://www.postgresql.org/message-id/510bf731.5020...@gmx.net
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
Best Wishes,
Chris Travers
http://www.2ndquadrant.com
PostgreSQL Services, Training, and Support
build something like this first as an extension
(perhaps with different function names) or first as a patch?
Best Wishes,
Chris Travers
http://www.2ndquadrant.com
PostgreSQL Services, Training, and Support
> On 15 September 2013 at 18:42 Andrew Dunstan wrote:
>
>
>
> On 09/14/2013 10:27 PM, chris travers wrote:
>
> Well, you could fairly easily build it as an extension as a POC. The
> main point of the API this is built on was to allow for extensions.
>
> The logic
his would be a frequently moving target and over years of billing,
the subset would be quite small compared to the full system (imagine, say, 50k
rows out of 20M).
Best Wises,
Chris Travers
>
> - Heikki
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
&
ether to merge the changes into the core,
This will be an interesting way to get into PostgreSQL hacking.
Best Wishes,
Chris Travers
>
> merlin
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http
","PS4","ACTION","FIRST PERSON
> SHOOTER"],"external_api_key":null}]'::JSON
>
> SELECT * FROM json_populate_recordset(null::varrm.item, '[{"title":"My
> Title","short_desc":"My Short Desc"
originally
thought but that just means it will take longer.
>
> cheers
>
> andrew
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
Best Wishes,
Chris Travers
http://www.2ndquadrant.com
PostgreSQL Services, Training, and Support
om the original host.
Am I missing something with this change?
Cheers,
Chris
o see what might be involved [attached], and would like
to hear people thoughts; good idea, bad idea, not like that! etc
Chris.
async_privileges_r0.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
" function.
Chris
On 20 May 2013 03:23, Tom Lane wrote:
> Chris Farmiloe writes:
> > I find the current LISTEN / NOTIFY rather limited in the context of
> > databases with multiple roles. As it stands it is not possible to
> restrict
> > the use of LISTEN or
o see what might be involved [attached], and would like
to hear people thoughts; good idea, bad idea, not like that! etc
Chris.
async_privileges_r0.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
g their upgrade then, maybe there
would need to be some kind of system to workaround this
Possibly some kind of "catch-all" channel, that enables implicit channel
names?
GRANT LISTEN, NOTIFY ON CHANNEL * TO PUBLIC; -- enabled by default for
backwards compat
NOTIFY xxxx; -- OK
Has there been any movement on this in the last couple years?
I could really use the ability to optimize across CTE boundaries, and it
seems like a lot of other people could too.
Is this some of that crufty code? Can
it be removed?
-- Chris
I'm on PostgreSQL 9.3. This should reproduce on any table with 100,000+
rows. The EXPLAIN ANALYZE shows many more rows getting scanned with LIMIT
2, but I can't figure out why.
Limit 1:
EXPLAIN ANALYZE WITH base AS (
SELECT *, ROW_NUMBER() OVER () AS rownum FROM a_big_table
), filter AS (
S
x...@thebuild.com (Christophe Pettus) writes:
> On Dec 7, 2010, at 2:43 PM, Josh Berkus wrote:
>> Because nobody sane uses OSX on the server?
>
> The XServe running 10.5 server and 9.0.1 at the other end of the
> office takes your remark personally. :)
I'd heard that Apple had cancelled XServe. [
t...@sss.pgh.pa.us (Tom Lane) writes:
> "Kevin Grittner" writes:
>> Robert Haas wrote:
>>> Simon Riggs wrote:
Note that DB2 uses the table modifier VOLATILE to indicate a
table that has a widely fluctuating table size, for example a
queue table.
>
>>> the fact that DB2 uses that
j...@nasby.net (Jim Nasby) writes:
> On Dec 10, 2010, at 6:18 PM, Jeff Janes wrote:
>> On Fri, Dec 10, 2010 at 3:09 PM, Hamza Bin Sohail wrote:
>>>
>>> Hello hackers,
>>>
>>> I think i'm at the right place to ask this question.
>>>
>>> Based on your experience and the fact that you have written
loureir...@gmail.com (Daniel Loureiro) writes:
>> You can believe whatever you want, that doesn't make it true.
> completely agree. Like yours, Its just my point of view, not the reality.
>
> I agree with some points here, but I wondering how many good ideas are
> killed with the thought: "this wil
t...@sss.pgh.pa.us (Tom Lane) writes:
> Robert Haas writes:
>> ... On the
>> other hand, there's clearly also a use case for this behavior. If a
>> bulk load of prevalidated data forces an expensive revalidation of
>> constraints that are already known to hold, there's a real chance the
>> DBA w
pete...@gmx.net (Peter Eisentraut) writes:
> I have often found myself wanting that psql automatically switch between
> normal and \x mode depending on the width of the output. Would others
> find this useful?
I haven't tested the patch, but that *does* sound generally useful.
It's no fun trying
pete...@gmx.net (Peter Eisentraut) writes:
> On mån, 2010-12-27 at 12:33 -0500, Andrew Dunstan wrote:
>> On a more general point, it would be useful to have some
>> infrastructure for running quality checks like this and publishing
>> the results. We should be way beyond the point where we rely on
pete...@gmx.net (Peter Eisentraut) writes:
> Implement remaining fields of information_schema.sequences view
>
> Add new function pg_sequence_parameters that returns a sequence's start,
> minimum, maximum, increment, and cycle values, and use that in the view.
> (bug #5662; design suggestion by Tom
nd went
looking for "hash_add() or similar. It's permissible to say "dumb
Chris".)
- If it's a collision, then mark collision in skip slot array, and
add to count
- After the walk
- Clean up hash table
- If nothing found, clean up skip s
robertmh...@gmail.com (Robert Haas) writes:
> On Mon, Jan 17, 2011 at 8:23 PM, Greg Smith wrote:
>> Quite. It's taken me 12 days of machine time running pgbench to find the
>> spots where this problem occurs on a system with a reasonably sized
>> shared_buffers (I'm testing against 256MB). It's
1 - 100 of 507 matches
Mail list logo
