Re: [HACKERS] scheduler in core

hen i could just work the rest in pgAgent... so, is this idea (having some user processes be "tied" to postmaster start/stop) going to somewhere? it also could help if we you have processes LISTENing for NOTIFYs -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesorí

Re: [HACKERS] scheduler in core

y time this topic comes up in -hackers, > there are a significant number of people who don't think a scheduler > should be tied to the core code so we stopped assuming it ever would > be. > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > -- Enviado

Re: [HACKERS] scheduler in core

On Sat, Feb 20, 2010 at 7:32 PM, Dave Page wrote: > On Sun, Feb 21, 2010 at 12:03 AM, Jaime Casanova > wrote: >> On Sat, Feb 20, 2010 at 4:37 PM, Dave Page wrote: >>> On Sat, Feb 20, 2010 at 9:33 PM, Jaime Casanova >>> wrote: >>>> Hi, >>>&g

Re: [HACKERS] scheduler in core

On Sat, Feb 20, 2010 at 4:37 PM, Dave Page wrote: > On Sat, Feb 20, 2010 at 9:33 PM, Jaime Casanova > wrote: >> Hi, >> >> I'm trying to figure out how difficult is this > > Why not just use pgAgent? It's far more flexible than the design > you've s

[HACKERS] scheduler in core

ny workers as it needs pg_dump support -- dump every entry of the pg_job catalog as a CREATE JOB SQL statement or a create_job() function depending on what we decided ideas? comments? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistem

Re: [HACKERS] explain and PARAM_EXEC

width=4) Output: (SubPlan 1) SubPlan 1 -> Index Scan using pg_class_oid_index on pg_catalog.pg_class a (cost=0.00..8.27 rows=1 width=4) Output: a.oid Index Cond: (a.oid = subplan1.$0) -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y d

Re: [HACKERS] log_error_verbosity function display

t;        STATEMENT:  select * from lkjasdf; > i like this with or without the (), but maybe we are breaking client apps if change that -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pg

Re: [HACKERS] set the cost of an aggregate function

ery row cost (maybe multiplied to cpu_operator_cost or cpu_tuple_cost) and the final function cost should be applied just once, no? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hac

Re: [HACKERS] further explain changes

On Thu, Jan 28, 2010 at 4:18 PM, Robert Haas wrote: > On Sun, Jan 24, 2010 at 12:30 PM, Tom Lane wrote: >> Robert Haas writes: >>> On Sun, Jan 24, 2010 at 12:06 AM, Jaime Casanova >>>> why not let it go in ANALYZE, just as the sort info >> >>> It

Re: [HACKERS] further explain changes

ERBOSE) why not let it go in ANALYZE, just as the sort info -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your su

Re: [HACKERS] WARNING: pgstat wait timeout

On Wed, Jan 20, 2010 at 9:32 PM, Jaime Casanova wrote: > On Wed, Jan 20, 2010 at 6:20 PM, Sergey E. Koposov wrote: >> Hello hackers, >> >> I've recently hit the message "WARNING:  pgstat wait timeout" with PG 8.4.2. > > i see the same yeste

Re: [HACKERS] WARNING: pgstat wait timeout

ed to that patch and was thinking in recompile without the patch but hadn't time, obviously i was wrong -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-ha

Re: [HACKERS] lock_timeout GUC patch

N32 > Introduced assign_lock_timeout() GUC validator function that allows > setting the value only from the wired-in-default (0) or from SET statements. > > Comments? > > Best regards, > Zoltán Böszörményi > > -- > Bible has answers for everything. Proof: > "But

Re: [HACKERS] lock_timeout GUC patch

2010/1/15 Boszormenyi Zoltan : > Jaime Casanova írta: >> 2010/1/13 Boszormenyi Zoltan : >> >>>> Your smaller patch is attached, with the above strangeness. :-) >>>> >>>> ok, the patch is more simpler than before and seems to be doing things r

Re: [HACKERS] lock_timeout GUC patch

2010/1/13 Boszormenyi Zoltan : >> >> Your smaller patch is attached, with the above strangeness. :-) >> you still had to add this parameter to the postgresql.conf.sample in the section about lock management -- Atentamente, Jaime Casanova Soporte y capacitación de Pos

Re: [HACKERS] [PATCH] remove redundant ownership checks

know exactly what the plan is? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.po

Re: [HACKERS] lock_timeout GUC patch

case. > if you try to open a critical system index and it doesn't exist is clearly a signal of corruption, if you can't lock it it's just a concurrency issue... don't see why they both should have the same level of message -- Atentamente, Jaime Casanova Soporte y capacit

Re: [HACKERS] lock_timeout GUC patch

actually think that PANIC is too high for this... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] patch to implement ECPG side tracing / tracking ...

2010/1/12 Hans-Jürgen Schönig : > hi, > > this patch implements SQL side tracing / tracking of statements and > statement execution times. > why is this better than using the "auto explain" module? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL

Re: [HACKERS] Congrats Alvaro!

2010/1/9 Devrim GÜNDÜZ : > > Congrats Alvaro for his second daughter ! > +1 -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [pgsql-www] [HACKERS] tribble.postgresql.org - planned maintenance downtime

On Wed, Jan 6, 2010 at 12:42 PM, Alvaro Herrera wrote: >> >> Oh, so you'r ecoming to FOSDEM? > > February this year?  No way :-(  I'm probably anchored at home until > August or so ... > had your baby born now? -- Atentamente, Jaime Casanova Soporte y cap

Re: [HACKERS] Type modifiers for DOMAIN

n? This feature would be useful for migration > from other DBMSes that have non-standard data types. > +1 -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailin

Re: [HACKERS] patch - per-tablespace random_page_cost/seq_page_cost

if there's another issue.  Updated > patch attached. > ah! yeah! it has been a long holiday ;) -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-ha

Re: [HACKERS] patch - per-tablespace random_page_cost/seq_page_cost

in syscache.c -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] about some parameters

pparently not looking 3) seems like the idea of this GUC started as a multiplier for all *_cost parameters but ended being just for random_page_cost 4) ... and that Tom has three hands (http://archives.postgresql.org/pgsql-hackers/2006-05/msg01346.php) -- Atentamente, Jaime Casanova Soport

[HACKERS] about some parameters

tablespace what will mean to change a tablespace seq_page_cost? it will be relative to the general one? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Distinguish view and table problem

hink this is somewhat necesary to read: http://wiki.postgresql.org/wiki/Developer_FAQ#Technical_Questions and of course look at other files that acces that kind of info, for example look at AlterTableNamespace() funtion in src/backend/commands/tablecmds.c to find out for a complete example to identify t

Re: [HACKERS] Re: [COMMITTERS] pgsql: Allow read only connections during recovery, known as Hot

Standby. >> >> Congratulations!  And, may I be the first to say - woo hoo! > > +1! > +1 i will start to play with HS in windows -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +5938717115

Re: [HACKERS] Syntax for partitioning

r this will arrive in the next commitfest so maybe you have more time then -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] XLogInsert

On Thu, Dec 10, 2009 at 3:58 PM, Alvaro Herrera wrote: > Jaime Casanova escribió: >> On Wed, Dec 9, 2009 at 9:39 AM, Tom Lane wrote: >> > so I'd like some independent confirmation that it does. >> > >> >> what kind of tests could show that? or si

Re: [HACKERS] thread safety on clients

On Thu, Dec 10, 2009 at 11:33 PM, Jaime Casanova wrote: > On Thu, Dec 10, 2009 at 11:22 PM, Tom Lane wrote: >> >> My bet is that the real problem was a build inconsistency in >> the backend.  Does "make distclean" and rebuild make it go away? >> > > act

Re: [HACKERS] Largeobject Access Controls (r2460)

of pg_largeobject. besides if a normal user can read from pg_class why we deny pg_largeobject -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] thread safety on clients

aries and installed it in just created directory... i will try again now with the patch Bruce just committed -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-

Re: [HACKERS] XLogInsert

On Wed, Dec 9, 2009 at 9:39 AM, Tom Lane wrote: > so I'd like some independent confirmation that it does. > what kind of tests could show that? or simply running pgbench several times for 15 minutes each run could show any benefit? -- Atentamente, Jaime Casanova Soporte y capa

[HACKERS] thread safety on clients

he current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. """ if i remove the -j option then it runs without a problem -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Gua

Re: [HACKERS] XLogInsert

in the next hours... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] ECPG patch 2, SQLDA support

On Mon, Nov 16, 2009 at 5:59 AM, Boszormenyi Zoltan wrote: > New version: rebased to current CVS. > This one no longer applies to HEAD, could you update it please? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuad

Re: [HACKERS] New PostgreSQL Committers

On Mon, Dec 7, 2009 at 5:49 AM, Dave Page wrote: > > The new committers are: > > Robert Haas > Simon Riggs > Greg Stark > ITAGAKI Takahiro > > Congratulations! > +1 -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de si

Re: [HACKERS] [PATCH] Largeobject Access Controls (r2460)

ut we have changed it a lot of times so if anyone has a better idea now is when you have to speak -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@post

Re: [HACKERS] [PATCH] Largeobject Access Controls (r2432)

napShot is calling the other one with SnapShotNow, can't we simply call it that way and drop the version of the functions that doesn't have that parameter? + pg_largeobject_aclmask(Oid lobj_oid, Oid roleid, + AclMode mask, AclMaskHow how) + pg_largeobject_aclch

Re: [HACKERS] set the cost of an aggregate function

2009/11/30 Jaime Casanova : > Hi, > > why we can't do $subject? it could have any benefit on the planner? > seems like while we can set the cost of the state transition function, that cost is not propagated... -- Atentamente, Jaime Casanova Soporte y capacitación de Post

[HACKERS] set the cost of an aggregate function

Hi, why we can't do $subject? it could have any benefit on the planner? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To

Re: [HACKERS] Syntax for partitioning

er some more explicit syntax for this not just reusing a table >      PARTITION name VALUES LESS THAN { range_upper | MAXVALUE } >    | PARTITION name VALUES IN ( list_value [,...] | DEFAULT ) > i remember someone making a comment about actually using operators instead of LESS THEN an

Re: [HACKERS] next CommitFest

On Wed, Nov 11, 2009 at 4:40 PM, Robert Haas wrote: > On Wed, Nov 11, 2009 at 4:21 PM, Jaime Casanova > wrote: >> why we need a full time manager at all? >> why not simply use -rrreviewers to track the status of a patch? of >> course, we hope the author or reviewer

Re: [HACKERS] next CommitFest

that patch... and an email every week or every few days saying how many patches are, how many are being reviewed, how many hasn't been reviewed, and so on... then the remaining work should be not that much, no? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y d

[HACKERS] total execution time as reported by auto_explain

:32:41 GMTLOG: duration: 779.938 ms plan: Sort (cost=1943.99..1967.38 rows=9355 width=466) (actual time=235.655..269.061 rows=4997 loops=1) -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 2009-11

Re: [HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

mportant enough please go for it -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.p

Re: [HACKERS] Patch set under development to add usage reporting.

ughts on this. > There is still some hard work to be done.  We have an INFORMATION > SCHEMA implementation for MySQL 5.x, but not yet for PostgreSQL. > we have an information schema since 7.4 (http://www.postgresql.org/docs/7.4/static/information-schema.html) -- Atentamente, Jaime Casanova S

Re: [HACKERS] License clarification: BSD vs MIT

On Mon, Oct 26, 2009 at 10:40 AM, Dave Page wrote: > On Mon, Oct 26, 2009 at 3:36 PM, Jaime Casanova > wrote: >> On Mon, Oct 26, 2009 at 8:08 AM, Simon Riggs wrote: >>> >>> ISTM we should apply to OSI for approval of our licence, so we can then >>>

Re: [HACKERS] License clarification: BSD vs MIT

in the case both licenses are "roughly equivalent", because users are afraid of any changes. if we simply change our license for no good reason we will have a ton of questions about if PostgreSQL is being sold just as MySQL was... -- Atentamente, Jaime Casanova Soporte y capacitación de

Re: [HACKERS] Client application name

besides, as Robert mention, because of pooler connections using a GUC is more appropiate... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.

Re: [HACKERS] Client application name

On Tue, Oct 13, 2009 at 11:55 AM, Robert Haas wrote: > > What happens if we want to change the application name after the fact? >  Consider the case where there is a connection pooler between the > database and application, for example. > good point... -- Atentamente, Jaime Cas

Re: [HACKERS] GRANT ON ALL IN schema

On Mon, Oct 12, 2009 at 1:42 PM, Tom Lane wrote: > > ALTER DEFAULT PRIVILEGES ... GRANT ... ON TABLES TO ... > this makes sense to me, because you want the default to affect all new tables not only a new single table. so, as someone once told, +1 from me ;) -- Atentamente, Jaime

Re: [HACKERS] GRANT ON ALL IN schema

hat you need for every type of object here */ + + } i think this is more readable -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@post

Re: [HACKERS] Writeable CTEs and side effects

On Wed, Oct 7, 2009 at 4:20 PM, Marko Tiikkaja wrote: > Jaime Casanova wrote: >> >> On Wed, Oct 7, 2009 at 4:08 PM, Marko Tiikkaja >> wrote: >>> >>> 1)      WITH t AS >>>       (UPDATE foo SET bar = bar+1 RETURNING *) >>>       SELECT

Re: [HACKERS] Writeable CTEs and side effects

sults... what the select reads from that results is another thing... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To

Re: [HACKERS] moving system catalogs to another tablespace

On Tue, Oct 6, 2009 at 9:43 AM, Alvaro Herrera wrote: > Jaime Casanova wrote: > >> now i think that what Euler shows me [1] is a fair compromise (this is >> to allow this only when in standalone mode with system catalogs >> allowed) otherwise we will have diferen

Re: [HACKERS] moving system catalogs to another tablespace

On Mon, Oct 5, 2009 at 10:26 PM, Tom Lane wrote: > Jaime Casanova writes: >> seems like the original idea was to forbid this in all system catalogs >> except pg_largeobject, what happen then? > > Nothing ... nobody got around to doing anything about it. > ah! well,

Re: [HACKERS] moving system catalogs to another tablespace

g00835.php seems like the original idea was to forbid this in all system catalogs except pg_largeobject, what happen then? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers ma

[HACKERS] moving system catalogs to another tablespace

? are there any reasons for this? i guess i still could this with symlinks, no? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Use "samehost" by default in pg_hba.conf?

l... to me the only reason it exists is to force me to change 'localhost' to '*' after installing, something i always do almost automaticaly =) -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171

Re: [HACKERS] Lock Wait Statistics (next commitfest)

the patch itself: you haven't documented either. what is the pg_stat_lock_waits view for? and what are those fieldx it has? i'll let this patch as "needs review" for more people to comment on it... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría

Re: [HACKERS] [PATCH] Largeobject access controls

will mark the patch as "ready for committer" -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [PATCH] Largeobject access controls

ission denied for largeobject 16453      < dose not prevent > it i'm not really sure the warnings are worth the trouble but if you want to do it then the NOTICE version should use another message... i'm not comfortable with a "permission denied" that is simply ignor

Re: [HACKERS] [PATCH] Largeobject access controls

functions but i think we can add them later if needed... > > Jaime Casanova wrote: >>> Do you think the "largeobject_compat_acl" is a meaningful name, instead? >> >> maybe something like "largeobject_security_controls"? > > It is important to conta

Re: [HACKERS] [PATCH] Largeobject access controls

On Tue, Sep 22, 2009 at 12:53 PM, Robert Haas wrote: > On Tue, Sep 22, 2009 at 1:29 PM, Jaime Casanova > wrote: >> have anyone better ideas about the name? if not, then go with >> pg_largeobject_meta > > I don't think there's anything wrong with calling it me

Re: [HACKERS] [PATCH] Largeobject access controls

> has an identical structure to the current pg_largeobject). > > However, it seems to me the pg_largeobject_acl is an incorrect name, > because it also contains the owner identifier which is a part of metadata, > but not an acl. > have anyone better ideas about the

Re: [HACKERS] [PATCH] Largeobject access controls

to put the GUC in the postgresql.conf file if you hope people know about it ;) it is not documented either About the code... - I don't like the name pg_largeobject_meta why not pg_largeobject_acl (put here any other name you like)? or there was a reason for that choose? -- Atentamente

Re: [HACKERS] [PATCH] Largeobject access controls

On Fri, Sep 18, 2009 at 8:29 PM, Stephen Frost wrote: > Jamie, > > How is the review for this coming?  Do you have any thoughts regarding > the new GUC? > Hi, sorry... these have been hard days... i'm just starting reviewing -- Atentamente, Jaime Casanova Soporte y capaci

Re: [HACKERS] Feedback on getting rid of VACUUM FULL

y reason that server came to that situation was a horribly fsm configuration and a bad design that forces an incredible amount of updates... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent

Re: [HACKERS] Logging configuration changes [REVIEW]

" > LOG:  Parameter "max_connections" cannot be changed without restarting the > server > LOG:  parameter "log_checkpoints" changed to "on" > ok, maybe this is not the most brilliant observation but someone has to say it... keep the same case in the word

Re: [HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

> Aahhh, correct you are Daniel son :) >>> >> >> ??? don't understand you ??? > > From the movie "karate kid"; oopps, should be Daniel San. > ah! got it... ;) -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y

Re: [HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

On Mon, Sep 14, 2009 at 2:20 PM, Andrew Chernow wrote: > Jaime Casanova wrote: >> >> On Mon, Sep 14, 2009 at 1:34 PM, Andrew Chernow wrote: >>> >>> Jaime Casanova wrote: >>>> >>>> i extracted the functions to connect that Heikki put on ps

Re: [HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

On Mon, Sep 14, 2009 at 1:55 PM, Tom Lane wrote: > Jaime Casanova writes: >> i put the new function at the end of the exports.txt file, there's a >> reason to renumber the exports to put it at the beginning with the >> other PQconnectdb function? > > Exports.

Re: [HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

On Mon, Sep 14, 2009 at 1:34 PM, Andrew Chernow wrote: > Jaime Casanova wrote: >> >> i extracted the functions to connect that Heikki put on psql in his >> patch for determining client_encoding from client locale and put it in >> libpq so i follow the PQconnectdb

Re: [HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

On Thu, Sep 10, 2009 at 12:01 AM, Jaime Casanova wrote: > On Mon, Jul 6, 2009 at 10:00 AM, Heikki > Linnakangas wrote: >> >> Could we >> have a version of PQconnectdb() with an API more suited for setting the >> params programmatically? The PQsetdbLogin() approach

[HACKERS] new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)

cts: > > PQconn *PQconnectParams(PQconninfoOption *params); > this sounds like a good idea, specially if we add new parameters to the conninfo string and want postgresql's client applications to use them. any one have a preference here? -- Atentamente, Jaime Casanova Soporte y capacitac

Re: [HACKERS] remove flatfiles.c

d yes the planner is not very clever about partitioning and certainly that is something we need to fix not something we have to live with... no that that will be easy but hey! we have very brilliant people here (you being one of them) -- Atentamente, Jaime Casanova Soporte y capacitación de Post

Re: [HACKERS] MySQL Compatibility WAS: 8.5 release timetable, again

ken stuff... just because mysql users think is wonderful to not have to write sane code... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] MySQL Compatibility WAS: 8.5 release timetable, again

be scary if we start supporting every single piece of code MySQL accepts -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make cha

Re: [HACKERS] 8.5 release timetable, again

not sure how to compare the databases - execute 60 of the 121 tests (or at least those that create tables and insert/update/delete the most data) - crash the server and replay the WAL - execute the rest of the tests and cross your fingers :) -- Atentamente, Jaime Casanova Soporte y capacitación de Post

Re: [HACKERS] Feature / Enhancement request.

o enable/disable the track of such changes -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http:/

Re: [HACKERS] Determining client_encoding from client locale

On Wed, Aug 19, 2009 at 11:08 AM, Jaime Casanova wrote: > On Tue, Aug 18, 2009 at 6:49 AM, Heikki > Linnakangas wrote: >> >> Hmm, are you sure you the right version of libpq is being loaded at >> runtime? What does "ldd ./test-libpq" say? >> > attach

Re: [HACKERS] Index-only quals

, BTW. > If an indexam has no gettuple function, there's no way it can return > data from the index. > to have two columns that can conflict is not error prone? why not make amhasgettuple an enum? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y des

Re: [HACKERS] Determining client_encoding from client locale

sql-hackers/2009-07/msg01501.php -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Hot standby and synchronous replication status

o make this *manually* in windows? maybe this is enough reason for a tool to make it... -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgr

Re: [HACKERS] Filtering dictionaries support and unaccent dictionary

On Fri, Aug 7, 2009 at 10:44 AM, Jaime Casanova wrote: > On Thu, Aug 6, 2009 at 10:46 PM, Robert Haas wrote: >> >> I am not sure whether this has been formally reviewed by anyone yet; >> do we think it's "Ready for Committer"? >> > > i was trying

Re: [HACKERS] pg_stat_activity.application_name

is there anyone working on this or have plans to work on this? if not, i will give it a try as soon as this commitfest ends -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mail

Re: [HACKERS] Filtering dictionaries support and unaccent dictionary

ts doesn't know how to test it -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://w

Re: [HACKERS] Fwd: [BUGS] fix: plpgsql: return query and dropped columns problem

alter table [add|drop] column... it seems it's good enough and is implementing tom's suggestions... can this be reviewed by a commiter? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sen

Re: [HACKERS] ECPG dynamic cursor, SQLDA support

On Sat, Jul 25, 2009 at 4:38 PM, Jaime Casanova wrote: > On Wed, Jun 24, 2009 at 4:51 AM, Boszormenyi Zoltan wrote: >> Hi, >> >> attached is our latest patch extending ECPG: >> > > haven't tested this nor reviewed the code in detail, just some little > que

Re: [HACKERS] ECPG dynamic cursor, SQLDA support

there some #if 0 added, why are those? seems like something that doesn't need to be added + #if 0 + #define SQLSET 19 + #define SQLMULTISET 20 + #define SQLLIST 21 + #define SQLROW 22 + #define SQLCOLLECTION 23 + #define SQLROWREF 24 + #endif -- Atentament

Re: [HACKERS] Merge Append Patch merged up to 85devel

explaining what the fix is or what it should behave? > > Yeah, if I knew how to fix them then this patch wouldn't be stuck > waiting for feedback... :( > and what's the problem with those if? as someone says before feel free to speak slowly and draw pictures ;) -- At

Re: [HACKERS] Merge Append Patch merged up to 85devel

ding already existing if, why are those? and if they need to be fixed why there isn't a comment explaining what the fix is or what it should behave? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 dro

Re: [HACKERS] Determining client_encoding from client locale

nt_encoding: SQL_ASCII and when executing the same script compiled in windows i get an error, it doesn't recognize the client_encoding option... $ ./test-libpq.exe "dbname=postgres user=postgres host=192.168.204.101 port=54329 client_encoding=latin1" Connection to database failed:

Re: [HACKERS] Determining client_encoding from client locale

nge first and the a second patch that changes client app that can use it -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes t

Re: [HACKERS] Determining client_encoding from client locale

make[3]: Leaving directory `/home/Administrador/pgsql/src/interfaces/libpq' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/Administrador/pgsql/src/interfaces' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/Administrador/pgsql/src' make: *** [all] Error 2 -- Aten

Re: [HACKERS] Determining client_encoding from client locale

he libpq library resides. (Again, the compiler will search some directories by default.) For maximum portability, put the -L option before the -lpq option. For example: cc -o testprog testprog1.o testprog2.o -L/usr/local/pgsql/lib -lpq """ which is clearly not accurate, we also nee

Re: [HACKERS] Determining client_encoding from client locale

s adding a dependency) gcc -o test-libpq test-libpq.o -L/usr/local/pgsql/head/lib -lpq -lpgport -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postg

Re: [HACKERS] Determining client_encoding from client locale

On Wed, Jul 22, 2009 at 9:58 PM, Jaime Casanova wrote: > On Wed, Jul 22, 2009 at 7:30 PM, Alvaro > Herrera wrote: >> Jaime Casanova wrote: >> >>> this little test compiles fine until i applied your patch :( >>> >>> postg...@casanova1:~/pg_releases/pgtes

<    1   2   3   4   5   6   7   8   9   >