The concern here is that in the actual production
situation, the only symptom was that the startup process just stopped. There
were no log messages or any other indication of what was going wrong.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postg
or.
-- If I increased max_locks_per_transaction to 15000, the problem didn't occur,
even if I bumped up the number of iterations in the first to 20000.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to yo
eation, without a release, but I would expect that to exhaust something else
first.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
> On Oct 9, 2017, at 18:21, Peter Geoghegan <p...@bowt.ie> wrote:
> What's the hot_standy_feedback setting? How about
> max_standby_archive_delay/max_standby_streaming_delay?
On, 5m, 5m.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list
e
of those transactions finally getting replayed on the secondary, only to have
another one come in right behind it...
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
lass, and they're clustered together. Could a
large number of temporary table creations that are being undone by an abort
cause this?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://
g away.
> Can you correlate where the standby is stuck with what
> was happening on the source?
There are definitely some mysterious functions being called, and I'll dig into
those.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgre
at number changing at all?
Increasing:
# select mode, count(*) from pg_locks where pid=5882 group by mode;
mode | count
-+---
ExclusiveLock | 1
AccessExclusiveLock | 8810
(2 rows)
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgs
On Oct 9, 2017, at 12:18, Christophe Pettus <x...@thebuild.com> wrote:
>
> #0 0x558812f4f1da in ?? ()
> #1 0x558812f4f8cb in StandbyReleaseLockTree ()
> #2 0x558812d718ee in ?? ()
> #3 0x558812d75520 in xact_redo ()
> #4 0x558812d7f71
xact_redo ()
#4 0x558812d7f713 in StartupXLOG ()
#5 0x558812f0e262 in StartupProcessMain ()
#6 0x558812d8d4ea in AuxiliaryProcessMain ()
#7 0x558812f0b2e9 in ?? ()
#8 0x558812f0dae7 in PostmasterMain ()
#9 0x558812d0c402 in main ()
--
-- Christophe Pettus
x...@thebuild.com
not a delay for
queries. The WAL receiver continues to operate normally, and we can see
sent_location / write_location / flush_location continue to move ahead in
parallel, with replay_location stuck in that WAL segment.
Suggestions on further diagnosis?
--
-- Christophe Pettus
x
oosing a
given index or preventing it from choosing one ?
What kind of other options do I have to solve this performance issue ?
Thanks in advance for any help,
Regards,
--
Christophe Escobar
it's
not guaranteed.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On May 24, 2016, at 1:16 PM, Gavin Flower <gavinflo...@archidevsys.co.nz> wrote:
> What does 'GCC' stand for?
Gulf Cooperative Council. :)
https://en.wikipedia.org/wiki/Gulf_Cooperation_Council
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing li
We have a database (PostgreSQL 9.3.10) which is reporting this error on a TOAST
table on a VACUUM. Is there a canonical way of repairing this? The table is
*huge*, so a VACUUM FULL or pg_dump / pg_restore is probably not going to work.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent
ere a standard way of handling this situation?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ver from this point, and decide on a full package,
rather than continuing this process here in -general.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
as gotten so out of
control (basically, people are being told to shut up left and right), that I
don't see a consensus is possible right now.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
h
On Jan 24, 2016, at 8:17 PM, Christophe Pettus <x...@thebuild.com> wrote:
> 2. Use the NOT VALID option on ALTER TABLE ... ADD constraint, which allows
> the addition of a constraint without actually checking its validity.
And note that you might miss some potential planner o
lopment of this
> feature, nobody is asking you to.
Participation does not need to be limited to copy-editing. Of all the ways to
develop a community CoC, we're engaged in just about the worst possible one
right now.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsq
llows the
addition of a constraint without actually checking its validity.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Jan 24, 2016, at 9:01 PM, Charles Clavadetscher
wrote:
> What is the point of having a check constraint that is not checked?
Well, it *is* checked going into the future; it's just not checked at the time
the constraint is added. Ultimately, you do want to fix
How does that person or entity resolve things? What confidentiality promises
are made?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
.
I'd respectfully suggest that we table the discussion of the CoC text at this
point, let the high passions moderate a bit, and talk about the process. That
is the detail in which the devils will live.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing
MODE, thus the question.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
date x set a='a';",,,"psql"
Note that it's waiting for a ShareLock, not an AccessExclusiveLock, thus my
question.
Just to clarify, my very specific question is about "AccessExclusiveLock".
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tuple when another process has done an explicit LOCK ACCESS EXCLUSIVE?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ails that
> can change from time to time.
Great, thank you!
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
!
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
is being created [...]
Thanks! I suppose my question then is: Besides slot creation, when is
pg_decode_startup called?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
On Jan 23, 2015, at 7:40 AM, Tim Smith randomdev4+postg...@gmail.com wrote:
re: (a)
see the documentation pertaining to 'jsonb indexing', to wit:
-- Find documents in which the key company has value Magnafone
SELECT jdoc-'guid', jdoc-'name' FROM api WHERE jdoc @ '{company:
Magnafone}';
the same thing.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
missed it...
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thank you very much for the insights (and how to read correctly a explain
:)).
There is a difference in data between the 2 databases, crons where running
on one and not the other.
But your insights enabled us to dive deeper, thanks !
2014-11-05 18:30 GMT+01:00 Tom Lane t...@sss.pgh.pa.us:
Hi,
We have 2 instances of PG, one in 9.1.1 and 9.1.14. They have the same
data, schema, PG configuration, and are almost identical machines, same
number of cores and memory, but different cloud provider. The data was
transferred with a pg_dump/pg_restore. We ran VACUUM ANALYSE, ANALYSE, and
be thought of as disaster recovery, not as a oh, third time this week
operation.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tomorrow.
Thus, I really don't recommend making an operational decision that the lost of
a tablespace's storage is considered something routine.
That being said, you can make it work today if it is critical that it do so.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general
for most users.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
cluster just for
this purpose.
It does seem to meet all of your needs in a very efficient way; setting up a PG
cluster is not that complex.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription
Are is the contents of the .backup file (generated by pg_stop_backup())
documented anywhere? (Some of it is self-explanatory, of course). If not, is
there a quick summary of what START WAL LOCATION, STOP WAL LOCATION, and
CHECKPOINT LOCATION are?
--
-- Christophe Pettus
x...@thebuild.com
---
82
(1 row)
In cases where you have more complex calendars (like lists of bank holidays),
you could join against a table of them, or use a function that determines
whether or not a particular day is holiday or not.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing
In a query plan, I noticed the following:
Join Filter: (((all_permissions.role_recursive AND (alternatives:
SubPlan 5 or hashed SubPlan 6)) OR (permitted_e.id = deployed_e.id)) AND (NOT
(SubPlan 13)))
What's the 'alternatives' line? Brand new to me!
--
-- Christophe Pettus
x
.)
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
,
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Le 19/09/2012 02:47, David Johnston a écrit :
There is no difference in your example. Conceptually though I
suggest using only table-table conditions in an ON clause and placing
any table-value conditions into the where.
This is how I use it usually.
The main time you get differences is
Le 19/09/2012 17:08, Merlin Moncure a écrit :
SELECT * FROM foo LEFT JOIN BAR ON foo.id = bar.id AND bar.col = 'something';
The difference here is that the filtering is now happening at join
time where the left join semantics are playing: always return foo and
return bar rows if and only if the
I'm looking for an article that explains the difference between these
constructs IN POSTGRESQL (the rules seem to differ from one DB to another) :
SELECT A.*
FROM A
JOIN B ON a.id=b.id AND A.somefield='somevalue'
and
SELECT A.*
FROM A
JOIN B ON a.id=b.id
WHERE A.somefield='somevalue'
I have
!
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
permissions. What you are looking for is:
GRANT ALL ON ALL TABLES IN SCHEMA Indexer TO Indexer;
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
connected to the primary without issue, so: Are these messages
something to be concerned over?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
have an ORDER BY clause in it; did you write
GROUP BY where you meant ORDER BY?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Greetings,
Is there a combination of options that will cause a hot standby replica to log
queries that are cancelled due to a replication timeout
(max_standby_streaming_delay)?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
'2011-09-29 18:00 WEST';
ERROR: invalid input syntax for type timestamp with time zone: 2011-09-29
18:00 WEST
LINE 1: select timestamp with time zone '2011-09-29 18:00 WEST';
What am I missing? Is the parser insisting on three-letter time zone
abbreviations? Should it be?
--
-- Christophe Pettus
On Sep 29, 2011, at 10:50 AM, Tom Lane wrote:
Christophe Pettus x...@thebuild.com writes:
I am baffled. Both PDT and WEST appear as valid timezone abbreviations, and
each have unique values, but:
Where do you see WEST as a valid timezone abbrevation?
Voila, Western Europe Summer Time
On Sep 29, 2011, at 11:44 AM, Steve Crawford wrote:
There are 56 records and 3 different offsets in pg_timezone_names for the
abbreviation 'CST'.
That's actually how this popped up for me; using 'IST' was giving rather
unexpected results...
--
-- Christophe Pettus
x...@thebuild.com
On Sep 29, 2011, at 12:11 PM, Tom Lane wrote:
IST is one of the ones where there's a real conflict, ie it means
different things to different people.
Indeed; just noting that the search for a non-conflicting abbreviation is what
lead me to find the WEST thing.
--
-- Christophe Pettus
x
is up and running, and
the temp file is writeable.
Any thoughts?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
imply a fixed offset, shouldn't the results be the same?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On May 8, 2011, at 11:40 AM, Adrian Klaver wrote:
No, PST has an offset of -8.
Head desk. Thank you.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
, Postgres is going to have to search
every partition, because it can't just from the partition constraint know which
entries will match and which do not until it looks inside every record.
Or did you mean 'statecode' to be a column in a different table, on which
you're joining?
--
-- Christophe Pettus
. Are you using connection pooling?
2. What's the application server environment?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
in the
current table are not allowed). The data type of the default
expression must match the data type of the column.
A trigger is the appropriate solution in this case.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
(probably not in the
path) and the registries are not written (nothing appears under
HKLM\SOFTWARE\)
Is there another check I can do?
Thanks
Christophe
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
Hi
IMHO, you should never store password in clear
If you store the last 5 crypted passwords, then you can make it comparing the
new password, crypted, to those 5 strings.
Regards
--
Christophe Doré
Implementation Product Manager
3 rue Marcel Allegot
92190 Meudon, France
The video archive for the 02/09 SFPUG meeting, Hot Standby and
Streaming Replication, is now available:
http://thebuild.com/blog/2010/05/06/sfpug-hot-standby-and-streaming-replication/
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general
this work, you can find it at
http://svn.postgresqlfr.org/repos/tools/geshi/trunk/
Regards,
--
Christophe Chauvet
Président d'Ornix (http://ornix.org)
Membres et Administrateur de PostgreSQLFr (http://postgresql.fr)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
composite keys poorly (PostgreSQL
handles them just fine), or are concerned about ORMs which don't
support them at all (like Django's) or support them badly.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
[mailto:r...@iol.ie]
Sent: mercredi 31 mars 2010 19:00
To: Christophe Dore
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] prevent connection using pgpass.conf
On 31/03/2010 16:32, Christophe Dore wrote:
Hi
We are building a solution using some dedicated postgresql servers
(and
dedicated C
Hi
We are building a solution using some dedicated postgresql servers (and
dedicated C++ and Java apps). For security reasons, we'd like to prevent
users to connect (from our apps at least) to those servers with
passwords stored in files such as pgpass.conf.
Is there any configuration that can
in a database, from arbitrary data, which may not be valid
based on the database's vision of data consistency.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
The video archive for the 12/08 SFPUG meeting, Operator Exclusion
Constraints, is now available:
http://thebuild.com/blog/2009/12/23/sfpug-operator-exclusion-constraints/
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general
The video archive for the 11/10 SFPUG meeting, Continuent Tungsten
with PostgreSQL, is now available:
http://thebuild.com/blog/2009/12/22/sfpug-continuent-tungsten-with-postgresql/
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general
Ah, you think you have all the links in an entry corrected... :) It's
fixed now, thanks!
On Dec 22, 2009, at 10:14 PM, Robert Hodges wrote:
Hi Christophe,
Thanks for posting the video, but the linked video appears to be
Josh Berkus lecturing on GUCS, which I believe was the previous
the best solution:
http://www.postgresql.org/docs/8.4/interactive/plpgsql-cursors.html
If you can be a bit more detailed about what you are trying to
accomplish, we can help you more.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general
. Presumably,
since you did some kind of computation that came up with the number
'4', you can assign that value instead of using the field a:
UPDATE test1 set a=4, b=4;
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
On Dec 19, 2009, at 3:34 PM, Andrus wrote:
FoxPro's and probably dBase's do it differently.
Of course, FoxPro and related are not actually relational databases;
they're flat-file managers which use comamnds which somewhat resemble
the SQL syntax.
--
-- Christophe Pettus
x
read
committed isolation mode actually means; I'd encourage you to read the
documentation.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
of a
normal table.
Just to be clear, temporary tables partake of the same logic as
regular tables; for example, even a TEMPORARY ON COMMIT DROP table can
be used with savepoints within a transaction.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list
connection?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi
Why don't use etckeeper ?
Regards,
http://joey.kitenet.net/code/etckeeper/
Le 03/11/09 23:41, JP Fletcher a écrit :
Hi,
We manage hundreds of clusters and a handful of distinct pg_hba.conf
files across several sites. We are mostly satisfied with our
automated method of management, but
On Oct 20, 2009, at 8:32 AM, Viktor Rosenfeld wrote:
@Christophe, I enjoyed your talk very much, particularly because I
learned about pgfouine, which from the looks of it, will make my
current
project vastly simpler. So, thank you.
You should really thank Josh Berkus; he's the one who
On Oct 19, 2009, at 10:49 AM, Gerhard Wiesinger wrote:
None of the function is declared VOLATILE. Any other idea?
If they are not declared with a volatility category at all, the
default is VOLATILE. Is that a possibility?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql
reasonable to just make start an vacuum upon recovery from an
immediate shutdown an operational procedure, rather than something PG
does automatically?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
?
Thanks!
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Oct 19, 2009, at 4:39 PM, Scott Ribe wrote:
On OS X it definitely does; on other platforms it may not since
supported
encodings are platform-dependent.
The Centos version knows about it as well; thanks, that's the perfect
solution.
--
-- Christophe Pettus
x...@thebuild.com
The video archive for the 10/13 SFPUG meeting, The Mighty GUCS: A
guide to the essential PostgreSQL settings you need to know, is now
available:
http://thebuild.com/blog/2009/10/16/the-mighty-gucs/
It's also available on Vimeo:
http://vimeo.com/7109722
--
-- Christophe
On Oct 17, 2009, at 2:05 AM, Gerhard Wiesinger wrote:
Can you also upload the sample config files and the presentation.
Josh Berkus is on the road right now, but I'm sure he'll upload them
quite soon.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list
On Oct 16, 2009, at 10:04 AM, decibel wrote:
Out of curiosity, did you look at doing hints as comments in a query?
I don't think that a contrib module could change the grammar.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
On Oct 15, 2009, at 8:20 AM, Nathan Boley wrote:
http://encodestatistics.org/publications/statistics_and_postgres.pdf
Is there a better place for this?
For now, I'll add it to the Vimeo page.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql
?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi,
The video from Statistics and Postgres — How the Planner Sees Your
Data, the September 8, 2009 meeting of the SFPUG, is now available on
Vimeo:
http://vimeo.com/7051082
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general
there shortly
as well.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
results, as i have many fields to use for ranking.
You are correct that there are only four weights. Each weight,
however, can be assigned to any number of fields; you are not limited
to just four fields (if I understand your comment correctly).
--
-- Christophe Pettus
x...@thebuild.com
On Oct 11, 2009, at 1:14 AM, Devrim GÜNDÜZ wrote:
http://download.fedora.redhat.com/pub/epel/5/i386/repoview/letter_u.group.html
http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/letter_u.group.html
Many thanks; it was a 32 vs 64 bit library problem, solved.
--
-- Christophe
a percentage from
0% to 99%.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
to `uuid_export'
Any thoughts?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
, but not finding the uuid_export function inside
of it.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
, is
that you can't create an array of them.)
In response to the other email, DECIMAL is definitely the better
solution for what you are looking for.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription
reasonable data checking into the database as
you can.
Peter Eisentraut's suggestion of just not putting a scale or precision
on the type at all and using CHECK to validate the values is also a
fine way of handling it.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general
1 - 100 of 235 matches
Mail list logo