On 05/19/2017 01:57 PM, Micky Hulse wrote:
Wow, so many helpful replies already! Thanks everyone! I'm going to do
my best at answering questions … Starting from the first email reply.
:)
What version of Postgres, OS and how was it installed?
PostgreSQL 9.3.9 on i686-redhat-linux-gnu, compil
On Fri, May 19, 2017 at 2:43 PM, Paul Jungwirth wrote:
> On 05/19/2017 02:25 PM, Micky Hulse wrote:
>
>> Awesome, that worked!
>>
>> SET search_path TO myschema, public;
>>
>> Thanks to everyone for the help! I really appreciate it. :)
>>
>
> Glad you figured it out! Setting the seach_path is
On 05/19/2017 02:25 PM, Micky Hulse wrote:
Awesome, that worked!
SET search_path TO myschema, public;
Thanks to everyone for the help! I really appreciate it. :)
Glad you figured it out! Setting the seach_path is often a good thing to
put in your ~/.psqlrc so you don't run into the same
On Fri, May 19, 2017 at 2:09 PM, Micky Hulse wrote:
>> If you find that the type isn't in the public schema, try setting your
>> schema search path so that the function can locate it, e.g.:
>> SET search_path TO foo, public;
Awesome, that worked!
SET search_path TO myschema, public;
Thanks
On Fri, May 19, 2017 at 2:09 PM, Micky Hulse wrote:
> Cool! Dumb question, but is foo the schema or the type?
Doh! I see now that foo is the schema! Thanks again Paul!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgre
On Fri, May 19, 2017 at 1:31 PM, David G. Johnston
wrote:
> Short answer here is that whomever is calling that function needs to ensure
> that their search_path is setup so that the type can be found somewhere in
> it. Your desire for obscurity means you are pretty much on the hook for
> figuring
Hello and thanks for the help!
On Fri, May 19, 2017 at 1:25 PM, Paul Jungwirth
wrote:
> It sounds like the type might be in a different schema. You can say \dn to
> see the schemas in your database, and \dT+ will show the types along with
> their schema. You could also do \dT+ foo.* to see all th
On Fri, May 19, 2017 at 2:04 PM, Eric Hill wrote:
> I am pleased to report that with Merlin's suggestion of using the
> pg-large-object middleware, I have a test case now showing that I can write a
> 25MB buffer from Node.js to Postgres in roughly 700 milliseconds. Here is
> the JavaScript cod
Wow, so many helpful replies already! Thanks everyone! I'm going to do
my best at answering questions … Starting from the first email reply.
:)
On Fri, May 19, 2017 at 1:20 PM, Adrian Klaver
wrote:
>> sudo -i -u username
> You should not need to do above.
>> psql -U otherusername -d database
> Ju
On Fri, May 19, 2017 at 1:06 PM, Micky Hulse wrote:
Short answer here is that whomever is calling that function needs to
ensure that their search_path is setup so that the type can be found
somewhere in it. Your desire for obscurity means you are pretty much on
the hook for figuring out the rig
On 05/19/2017 01:06 PM, Micky Hulse wrote:
ERROR: type "xxx_xxx_x" does not exist
LINE 1: DECLARE results xxx_xxx_x;
It sounds like the type might be in a different schema. You can say \dn
to see the schemas in your database, and \dT+ will show the types along
with their schema. You
On 05/19/2017 01:06 PM, Micky Hulse wrote:
Hello,
I hope this is the right list for me to ask questions about psql.
Please let me know if I am in the wrong place. :)
I am far from an advanced user of PostgreSQL, so please bear with me ...
I am working with an inherited database/codebase. I am
Hello,
I hope this is the right list for me to ask questions about psql.
Please let me know if I am in the wrong place. :)
I am far from an advanced user of PostgreSQL, so please bear with me ...
I am working with an inherited database/codebase. I am trying to call
this function via psql:
# SEL
I am pleased to report that with Merlin's suggestion of using the
pg-large-object middleware, I have a test case now showing that I can write a
25MB buffer from Node.js to Postgres in roughly 700 milliseconds. Here is the
JavaScript code, which is nearly verbatim from the example in the
pg-lar
Hmm indeed that seems to be the case. Thanks for the tip!
On 05/19/2017 04:10 PM, John R Pierce wrote:
On 5/19/2017 1:25 AM, cen wrote:
< 2017-05-15 17:00:41.861 CEST >LOG: parameter "archive_command"
changed to ""/opt/omni/lbin/pgsqlbar.exe" -stage %p -backup"
I believe /opt/omni is the d
On Thu, May 18, 2017 at 4:57 PM, Kang, Kamal
wrote:
> Hi all,
>
>
>
> I am trying to encrypt a string using Bouncy Castle PGP Java apis, Base64
> encode the encrypted string and then decrypt using pg_pub_decrypt but it is
> failing with error “Wrong Key”. Just wanted to know if this is doable or
On Fri, May 19, 2017 at 6:56 AM, Karl O. Pinc wrote:
> I think if I was to make an argument for doing something it would
> be based on reliability -- how many users can you give their
> own database before somebody leaves an open transaction hanging?
Yeah, I guess it's worth having on the list,
On 5/19/2017 1:25 AM, cen wrote:
< 2017-05-15 17:00:41.861 CEST >LOG: parameter "archive_command"
changed to ""/opt/omni/lbin/pgsqlbar.exe" -stage %p -backup"
I believe /opt/omni is the default installation path for HP Data
Protector, formerly known as OmniBack. That comprehensive backu
On 05/19/2017 01:25 AM, cen wrote:
Every single day at exactly the same hour I get this in my pg_log:
< 2017-05-15 17:00:29.517 CEST >FATAL: pg_hba.conf rejects connection
for host "...", user "postgres", database "template1", SSL off
< 2017-05-15 17:00:29.571 CEST >WARNING: archive_mode ena
Hello,
This idea has been raised more or less before as well as the problems it would
solve. These are old, but IMHO the problem remains:
https://www.postgresql.org/message-id/24293.1272638299%40sss.pgh.pa.us
https://www.postgresql.org/message-id/D86CC5D8-C65A-4196-BB94-91614A814D29%40gtwm.co.u
On Fri, 19 May 2017 01:52:00 -0500
"Karl O. Pinc" wrote:
> On Thu, 18 May 2017 12:04:42 -0500
> Kevin Grittner wrote:
>
> > On Thu, May 18, 2017 at 11:07 AM, Karl O. Pinc wrote:
> >
> > > ... Does PG
> > > now pay attention to database in it's SSI implementation?
> >
> > Well, it pays
On Fri, May 19, 2017 at 10:25:13AM +0200, cen wrote:
> < 2017-05-15 17:00:41.861 CEST >LOG: parameter "archive_command" changed to
> ""/opt/omni/lbin/pgsqlbar.exe" -stage %p -backup"
This is the line that you'll have to base your research on.
Also, you might want to check for a keylogger in th
Every single day at exactly the same hour I get this in my pg_log:
< 2017-05-15 17:00:29.517 CEST >FATAL: pg_hba.conf rejects connection
for host "...", user "postgres", database "template1", SSL off
< 2017-05-15 17:00:29.571 CEST >WARNING: archive_mode enabled, yet
archive_command is not se
On 2017-05-18 21:48, Rob Brucks wrote:
Hello Everyone,
I am unable to figure out how the trigger was able to successfully
create the table, but then fail creating the index. I would have
expected one thread to "win" and create both the table and index, but
other threads would fail when creating
24 matches
Mail list logo
