On Tue, Nov 5, 2024 at 4:44 PM Ron Johnson wrote:
> On Tue, Nov 5, 2024 at 4:45 PM Matt Zagrabelny wrote:
>
>> Greetings Pg folk,
>>
>> I've got a legacy app connecting to a legacy Pg database (9.4).
>>
>> I'd like to upgrade the database to Pg 15
Greetings Pg folk,
I've got a legacy app connecting to a legacy Pg database (9.4).
I'd like to upgrade the database to Pg 15, but when I connect and perform
some tasks in the app, I get:
ERROR: column d.adsrc does not exist at character 331
Some searching online yields that adsrc was removed i
On Sat, Oct 5, 2024 at 5:43 PM Adrian Klaver
wrote:
> On 10/5/24 15:04, Matt Zagrabelny wrote:
>
> > psql (15.8 (Debian 15.8-0+deb12u1))
> >
> >
> > Where did you install it from or where are you running it?
> >
> >
> > Installed from Debian
On Sat, Oct 5, 2024 at 3:12 PM Adrian Klaver
wrote:
> On 10/5/24 11:24, Matt Zagrabelny wrote:
> >
>
> >
> > Nope. I create the role (via puppet) and then add the GRANT
> > pg_read_all_data TO (via puppet).
> >
>
> > What is \drgS? I don't beli
On Sat, Oct 5, 2024 at 11:26 AM Adrian Klaver
wrote:
> On 10/5/24 09:04, Matt Zagrabelny wrote:
> >
> >
> > On Sat, Oct 5, 2024 at 10:27 AM Adrian Klaver > <mailto:adrian.kla...@aklaver.com>> wrote:
> >
> > On 10/5/24 07:13, Matt Zagr
On Sat, Oct 5, 2024 at 10:27 AM Adrian Klaver
wrote:
> On 10/5/24 07:13, Matt Zagrabelny wrote:
> > Hi David (and others),
> >
> > Thanks for the info about Public.
> >
> > I should expound on my original email.
> >
> > In our dev and test
hieve this desire?
Thanks for the help!
-m
On Sat, Oct 5, 2024 at 9:02 AM David G. Johnston
wrote:
> On Saturday, October 5, 2024, Matt Zagrabelny wrote:
>
>> Hello,
>>
>> I'd like to have a read-only user for all databases.
>>
>> I found the pg_read_
Hello,
I'd like to have a read-only user for all databases.
I found the pg_read_all_data role predefined role, which I granted to my RO
user:
GRANT pg_read_all_data TO ro_user;
...but I cannot connect to my database(s).
I'd like to not have to iterate over all the databases and "GRANT
CONNECT.
Hi Adrian,
Thanks for the reply!
On Mon, Jun 24, 2024 at 7:03 PM Adrian Klaver
wrote:
> On 6/24/24 17:00, Matt Zagrabelny wrote:
> > Greetings,
> >
> > I have a database that I recently changed the ownership for and now I am
> > attempting to drop the pre
Greetings,
I have a database that I recently changed the ownership for and now I am
attempting to drop the previous owner of the database:
test_db=# drop ROLE legacy_owner;
ERROR: role "legacy_owner" cannot be dropped because some objects depend
on it
DETAIL: privileges for schema public
I don
> Hi matt,
>
> This is my take. I guess this is also your solution ( encode(fteld,
> 'hex'): :macaddr )
>
> SELECT encode(fteld, 'hex'): :macaddr FROM ((VALUES
> (decode('aabbccddeeff', 'hex'
>
> AS x(field)
> --
> Boris
Greetings Pg folks,
I have a database schema (not mine) that uses bytea to represent a MAC
address. I'd like to create a view that casts that field into a MACADDR
type.
# \d lease4
Table "public.lease4"
Column │ Type │ Collation │ Nullable │
At the risk of starting a +1 snowball or a divergent argument...
On Tue, Jan 31, 2023 at 10:16 AM Raymond Brinzer
wrote:
> Greetings,
>
> There is (for me) a small speed bump in psql. I think it's worth
> mentioning, minor though it is, because psql is such a polished tool
> generally, and bec
On Tue, Aug 31, 2021 at 11:10 AM Tom Lane wrote:
>
> Matt Zagrabelny writes:
> > $ \C foo
> > Title is "foo".
>
> > How do I suppress the echo of "Title is..." from psql?
>
> The -q switch would do it ...
Thank you, Tom!
-m
Greetings,
I am using the \C command in psql to set a title for my table.
psql is echoing 'Title is "foo"'.
$ \C foo
Title is "foo".
How do I suppress the echo of "Title is..." from psql?
Thanks for any help!
Cheers,
-m
Greetings PG-users,
Scenario:
I am using FreeRADIUS to insert data to a PG database.
One of the pieces of data is an array of key value pairs. The array is
encoded with quoted-printable [0].
I'd like to ideally have the key-value pair put into a JSONB field.
Here is an example of the data enco
On Mon, Feb 1, 2021 at 7:19 PM Guillaume Lelarge
wrote:
>
>
> You're doing a left join, so I guess there's no row where
> call_records.timestamp::date = 2020-08-30. That would result with a NULL id.
>
>
Thanks for the excellent analysis everyone. I appreciate it!
Here is the documentation (for a
On Mon, Feb 1, 2021 at 6:35 PM Tom Lane wrote:
> Matt Zagrabelny writes:
> > On Mon, Feb 1, 2021 at 5:57 PM Rob Sargent
> wrote:
> >> You got one null from count(*) likely.
>
> > What is count(*) counting then? I thought it was rows.
>
> Yeah, but count(id)
On Mon, Feb 1, 2021 at 5:57 PM Rob Sargent wrote:
[...]
>
> You got one null from count(*) likely.
>
What is count(*) counting then? I thought it was rows.
-m
Greetings,
Is there a preferred method of counting rows?
count(*) vs count(field_name)
I have used count(*) for a long time and am hitting an inconsistency. At
least it is an inconsistency to me (I'm sure there is an explanation)...
INCORRECT OUTPUT (not desired results)
$ select calendar.entry
Hello,
I see the --data-checksums option for initdb. Is it possible to use
--data-checksums after the cluster has been initialized? I'm guessing
"not", but thought I'd ask.
I'm running v12 on Debian.
Thanks for any help!
-m
On Thu, Jun 4, 2020 at 12:56 AM Laurenz Albe
wrote:
> On Thu, 2020-06-04 at 16:41 +1200, Thomas Munro wrote:
> > There's no doubt it's useful, and it's also part of the SQL spec,
> > which says you can do catalog.schema.table. I would guess that we
> > might get that as a byproduct of any projec
+1
On Wed, Feb 5, 2020 at 9:15 PM Ahmed, Nawaz (Fuji Xerox Australia)
wrote:
>
> +1
>
> -Original Message-
> From: Vik Fearing
> Sent: Thursday, 6 February 2020 1:55 PM
> To: pgsql-general@lists.postgresql.org
> Subject: POLL: Adding transaction status to default psql prompt
>
> Hello,
>
Greetings,
I've searched the internet and also the pgsql-general list for an answer to
this question, but couldn't find one.
Is there a continuation character for meta commands in psql?
I've seen mention that a caret (^) could be used, but it didn't work
correctly and the psql man page makes no
Hey Rich,
On Tue, Feb 12, 2019 at 4:24 PM Rich Shepard
wrote:
> The query is to return the latest next_contact date for each person. Using
> the max() aggregate function and modeling the example of lo_temp on page 13
> of the rel. 10 manual I wrote this statement:
>
I use DISTINCT ON and ORDER
On Fri, Dec 7, 2018 at 7:42 AM Arthur Zakirov
wrote:
> On 07.12.2018 01:34, Matt Zagrabelny wrote:
> >
> >
> > On Thu, Dec 6, 2018 at 4:24 PM Alvaro Herrera > <mailto:alvhe...@2ndquadrant.com>> wrote:
> >
> > Sure, just define a pg_service.conf
On Thu, Dec 6, 2018 at 4:24 PM Alvaro Herrera
wrote:
> On 2018-Dec-06, Matt Zagrabelny wrote:
>
> > I'd rather do:
> >
> > psql foo
> >
> > and have it know that I connect to foo on host db-host-1.example.com.
> >
> > Is this possible with psq
Greetings,
I'm setting up my workstation to use "gss" for auth to a variety of Pg
systems on different hosts.
I'd rather not have to specify the "-h" for a connection:
psql -h db-host-1.example.com foo
I'd rather do:
psql foo
and have it know that I connect to foo on host db-host-1.example.co
On Tue, Jul 31, 2018 at 9:21 AM, Tom Lane wrote:
> "Lu, Dan" writes:
> > Question:
> > Can be a variable like `hostname` derived from Unix shell or
> I have to hardcode the name of the host like " include
> /nfs/global/postgres-host123.cnf
>
> Nope, you'd have to hard-code it.
>
> Of course, yo
On Wed, May 9, 2018 at 3:05 AM, Pavel Stehule
wrote:
>
>
> 2018-05-09 9:59 GMT+02:00 John McKown :
>
>> I just wanted to throw this out to the users before I made a complete
>> fool of myself by formally requesting it. But I would like what I hope
>> would be a minor change (enhancement) to the p
On Wed, Dec 20, 2017 at 9:30 PM, support-tiger
wrote:
>
> No, the docs for understanding hba_conf are not good (yes we can read and
> are fairly smart) - we made suggestions the last time for several case
> examples and were ignored - okay, simplicity of pouchdb/couchdb is
> getting our atten
31 matches
Mail list logo