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@postgresql.org)
To mak
ased max_locks_per_transaction to 15000, the problem didn't occur,
even if I bumped up the number of iterations in the first to 2.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
t 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 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 (pgsql-general@post
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
nd 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://www.postgresql.org/mailpref/pgsql-general
rrelate 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@postgresql.org)
To
ng 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 pgsql-general maili
On Oct 9, 2017, at 12:18, Christophe Pettus wrote:
>
> #0 0x558812f4f1da in ?? ()
> #1 0x558812f4f8cb in StandbyReleaseLockTree ()
> #2 0x558812d718ee in ?? ()
> #3 0x558812d75520 in xact_redo ()
> #4 0x558812d7f713 in StartupXLOG ()
> #5
d7f713 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
--
Sent via pgsq
it's 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 P
ck, which will cause an index update.
The important thing to remember is that the process you are describing (in
which indexes are not updated unless a column involved in the index changes) is
an optimization, Heap-Only Tuples. It's a very common optimization, but it's
not guaranteed.
On May 24, 2016, at 1:16 PM, Gavin Flower 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 list (pgsql-general@postgresql
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
Is there 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
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 the data, but this
makes it
On Jan 24, 2016, at 8:17 PM, Christophe Pettus 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 optimizations this way, as
the p
hout 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
sion has 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:
http://www.postgresql.org/mailpref/pgsql-general
he development 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 pgsql-g
t, 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
y 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 list (pgsql-general@postgres
ity 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
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
,,"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
message implies there is such a thing as
an AccessExclusiveLock on a tuple, which is new to me. I wasn't able to
produce this message experimentally doing various combinations of UPDATE
statements and SELECT FOR UPDATEs, or even with explicit LOCK ACCESS EXCLUSIVE
MODE, thus the questi
o lock
a 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
reated [...]
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://www.postgresql.org/mailpref/pgsql-general
e?
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
; is not quite 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
On Jan 23, 2015, at 7:40 AM, Tim Smith 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"}';
>
> No
I've 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
gly suggest that relying on definition #2, while absolutely correct,
is a poor operational decision 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
future, but I don't think there's any guarantee that the
procedure that works today will work 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
pears, but that
should 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
le database 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 c
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
ACT(dow FROM day) BETWEEN 1 AND 5;
count
---
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...@t
ews.)
--
-- 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 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!
--
-- Christo
ema.
Best,
--
-- 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
hanks!
--
-- 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
e their own 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/mai
m
archive",""
All of these are on _vm relations. The recovery completed successfully and the
secondary connected to the primary without issue, so: Are these messages
something to be concerned over?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-gener
wn does't actually 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
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
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...
--
-- Christo
On Sep 29, 2011, at 10:50 AM, Tom Lane wrote:
> Christophe Pettus 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
time zone '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
pback interface is
unfiltered for UDP. The stats collector process itself 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
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.postgres
0:00-07
2011-03-13 03:00:00-07
(2 rows)
--
But if "PST" really did 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
every record.
Or did you mean 'statecode' to be a column in a different table, on which
you're joining?
--
-- 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
erious an issue.
1. 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
mns 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.or
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 l
systems that handle 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@postgresq
ew records 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.pos
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 (pgs
vious month.
BTW, since doing the Tungsten talk in early November we have also
implemented support for clusters using Londiste. We’ll do some
talks about it in the new year.
Cheers, Robert Hodges
(aka one of the Tungsten guys)
On 12/22/09 10:08 PM PST, "Christophe Pettus"
wro
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 (pgs
is probably 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
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
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.
--
-- Christo
ay, though. 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.
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
ut with the lifetime 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-
--
-- 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
e who gave the talk.
I just run the camera. :)
Josh has the slides and sample files, and I'm sure he'll post them
shortly. I know he's been busy with a client emergency and the
PostgreSQL conference this weekend.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via p
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...@thebuil
dings?
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
ewhat
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
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
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 ma
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
-
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@postgresq
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 (
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 (pgs
le in the index?
--
-- 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
available 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
just fine, 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
t+0x7): undefined reference 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
s presumably 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
sable to put as much 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
he only limitation, right now, 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@p
, the basic sales
tax rate in Los Angeles is 9.75%, so 0.0975. (There are other
subtleties in sales tax calculation in California; feel free to ask
off-list if you want more utterly non-PostgreSQL-related detail. :) )
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-ge
test.test VALUES (1)
into a NUMERIC(5,1), what you are doing is inserting:
INSERT INTO test.test VALUES (1.0)
1.0 has six significant digits, rather than five, so the insert
fails.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql
A quick check of the source code (src/backend/utils/adt/numeric.c)
shows it's base 1, each "digit" represented as an int16. It's not
strictly speaking BCD, but there's no computational difference.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via p
On Oct 4, 2009, at 7:09 PM, Guy Rouillier wrote:
There is no reason why PG could not support packed decimal.
Is that not NUMERIC?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
e the advantage that you can install exactly what you
want (so, no being stuck with PG 8.0, for example).
--
-- 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 Sep 26, 2009, at 11:29 AM, Christophe Pettus wrote:
Of course, one can create a user that has no useful privileges on a
particular database, but is there a way of limiting a user to being
able to log into only a single one of, or a subset of, the databases
in a cluster?
Like, say
Of course, one can create a user that has no useful privileges on a
particular database, but is there a way of limiting a user to being
able to log into only a single one of, or a subset of, the databases
in a cluster?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql
n the $BODY$ when writing the function? In other
words: why to use the $ sign?
Regards
Bilal
--
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...@thebuil
rds "words" (i.e., are they
completely arbitrarily embedded in the text, or are they delimited in
some regular way)? If they are "words," you might consider using the
full text functionality to create an index of them, and searching
using that.
--
-- Christophe Pettus
x...@
On Aug 23, 2009, at 7:47 AM, Andrew Cooper wrote:
An employee can only have 1 manager/supervisor but the hierarchy can
be varying depths.
Traditionally, that's done by having a "supervisor" field as part of
the employee record, with either NULL or a special marker value to
indicate "no su
the database instead of calling one function, but it
wasn't significant enough to be a problem.)
Hope this helps!
--
-- 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,
The video of the August 11, 2009 SFPUG talk, featuring David Fetter's
presentation on windowing and common table expressions, is now up:
http://thebuild.com/blog/2009/08/13/sfpug-windowing-and-common-table-expressions/
--
-- Christophe Pettus
x...@thebuild.com
--
Sen
1 - 100 of 110 matches
Mail list logo